Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • V valueflows
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 42
    • Issues 42
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Value Flows
  • valueflows
  • Issues
  • #300

Closed
Open
Created Nov 27, 2018 by elf Pavlik@elf-pavlikOwner

Categorizing / classifying and specifying work and services.

Capturing from https://github.com/valueflows/valueflows/pull/296#discussion_r236713077

@elf-pavlik I would not use ResourceSpecification since we don't reference any resource from work flows and this would just make everything more confusing. Only flows which at event stage will reference an actual resource with affects should use vf:resourceConformsTo and reference specification of a resource which event will reference using vf:affects.

Assignee
Assign to
Time tracking