http://www.w3.org/2005/01/wf/flow#deliverable
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2005/01/wf/flow#Product
http://www.w3.org/2000/01/rdf-schema#label deliverable
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment Something which must be deliverered to accomplish this
http://www.w3.org/2000/01/rdf-schema#subPropertyOf http://www.w3.org/2005/01/wf/flow#dependent

https://mtp.linked.solutions/
http://xmlns.com/foaf/0.1/topic https://mtp.linked.solutions/wf

http://www.w3.org/2005/01/wf/flow#tracker
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2005/01/wf/flow#Tracker
http://www.w3.org/2000/01/rdf-schema#label tracker
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2005/01/wf/flow#Task
http://www.w3.org/2002/07/owl#inverseOf _:0
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property

http://www.w3.org/2005/01/wf/flow#task
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2005/01/wf/flow#Task
http://www.w3.org/2000/01/rdf-schema#label task
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property

http://www.w3.org/2005/01/wf/flow#successCriteria
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2001/XMLSchema#string
http://www.w3.org/2000/01/rdf-schema#label success criteria
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2005/01/wf/flow#Task
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2002/07/owl#DatatypeProperty
http://www.w3.org/1999/02/22-rdf-syntax-ns#Poperty
http://www.w3.org/2000/01/rdf-schema#comment A textual description of the successs critera. How when we know this is done?

http://www.w3.org/2005/01/wf/flow#affects
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2005/01/wf/flow#Task
http://www.w3.org/2000/01/rdf-schema#label affects
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2000/10/swap/pim/doc#Work
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property

http://www.w3.org/2005/01/wf/flow#asigneeClass
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2000/01/rdf-schema#Class
http://www.w3.org/2000/01/rdf-schema#label assignees must be
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2005/01/wf/flow#Tracker
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment When an issue is assigned, the assignee must be from this class

http://www.w3.org/2005/01/wf/flow#allowedTransitions
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/1999/02/22-rdf-syntax-ns#List
http://www.w3.org/2000/01/rdf-schema#label allowed transitions
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2005/01/wf/flow#State
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment The state machine is defined by these lists of transition allowed for each issue. (An interesting option in the Web is to make an allowed transition to a state in soemone else's ontology, which in turn allows transitions into many ontologies. So a finite state maxchine may become very large. In practice this means that a task handed off to another organization may be processed on all kinds of ways.)

http://www.w3.org/2005/01/wf/flow#issueCategory
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2000/01/rdf-schema#Class
http://www.w3.org/2000/01/rdf-schema#label issue category
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2005/01/wf/flow#Tracker
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment Issues may be categorized according to the subclasses of this class

http://www.w3.org/2005/01/wf/flow#Creation
http://www.w3.org/2000/01/rdf-schema#label creation
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2000/01/rdf-schema#Class
http://www.w3.org/2000/01/rdf-schema#comment A creation is a change from existence to non-existence a task. Typical properties include date and/or source (a document causing the transition), and a final state.
http://www.w3.org/2000/01/rdf-schema#subClassOf http://www.w3.org/2005/01/wf/flow#Change

http://www.w3.org/2005/01/wf/flow#screenShot
http://www.w3.org/2000/01/rdf-schema#label screen shot
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment An image taken by capturing the state of a computer screen, for example to demonstrate a problem
http://www.w3.org/2000/01/rdf-schema#subPropertyOf http://www.w3.org/2005/01/wf/flow#attachment

http://www.w3.org/2005/01/wf/flow#recipent
http://www.w3.org/2000/01/rdf-schema#range http://xmlns.com/foaf/0.1/Agent
http://www.w3.org/2000/01/rdf-schema#label to
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2005/01/wf/flow#Message
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property

http://www.w3.org/2005/01/wf/flow#issue
http://www.w3.org/2000/01/rdf-schema#label issue
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment A transition changes the state of the given issue.

http://www.w3.org/2005/01/wf/flow#issueClass
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2005/01/wf/flow#State
http://www.w3.org/2000/01/rdf-schema#Class
http://www.w3.org/2000/01/rdf-schema#label all issues must be in
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2005/01/wf/flow#Tracker
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment The class of issues which are allowed in this tracker. This is essemtial to the operation of the tracker, as it defines which states an issue can be in. (The issueClass must be a disjointUnionOf the state classes)

http://www.w3.org/2005/01/wf/flow#dateDue
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2001/XMLSchema#date
http://www.w3.org/2000/01/rdf-schema#label due
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2005/01/wf/flow#Task
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2002/07/owl#DatatypeProperty
http://www.w3.org/1999/02/22-rdf-syntax-ns#Poperty
http://www.w3.org/2000/01/rdf-schema#comment The date this task is due.

http://www.w3.org/2005/01/wf/flow#message
http://www.w3.org/2000/01/rdf-schema#label message
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment A message about this. Attached for information.
http://www.w3.org/2000/01/rdf-schema#subPropertyOf http://www.w3.org/2005/01/wf/flow#attachment

http://www.w3.org/2005/01/wf/flow#goalDescription
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2001/XMLSchema#string
http://www.w3.org/2000/01/rdf-schema#label goals
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2005/01/wf/flow#Task
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2002/07/owl#DatatypeProperty
http://www.w3.org/1999/02/22-rdf-syntax-ns#Poperty
http://www.w3.org/2000/01/rdf-schema#comment A textual description of the goals of this product, etc.

http://www.w3.org/2005/01/wf/flow#transactionStore
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2000/10/swap/pim/doc#Document
http://www.w3.org/2000/01/rdf-schema#label transaction store
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2005/01/wf/flow#Tracker
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment An appendable document. Transactions and messsages can be written into here

http://www.w3.org/2005/01/wf/flow#stateStore
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2000/10/swap/pim/doc#Document
http://www.w3.org/2000/01/rdf-schema#label state store
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2005/01/wf/flow#Tracker
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment A read-write document. The state of the issues is modified here. When you set up a trcaker, thgis must be set to point to a writeble data resource on the web.

http://www.w3.org/2005/01/wf/flow#final
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2005/01/wf/flow#State
http://www.w3.org/2000/01/rdf-schema#label to
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2005/01/wf/flow#Transition
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property

http://www.w3.org/2005/01/wf/flow#testData
http://www.w3.org/2000/01/rdf-schema#label test data
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment A file which can be used as inpiut to a test or to demonstrate a problem.
http://www.w3.org/2000/01/rdf-schema#subPropertyOf http://www.w3.org/2005/01/wf/flow#attachment

http://www.w3.org/2005/01/wf/flow#description
http://www.w3.org/2000/01/rdf-schema#label description
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment The description, definition, or abstract. Information explaining what this is. Not arbitrary comment about anything, only about the subject. (Use this property for anything. There is no domain restriction.).

http://www.w3.org/2005/01/wf/flow#subscriber
http://www.w3.org/2000/01/rdf-schema#range http://xmlns.com/foaf/0.1/Agent
http://www.w3.org/2000/01/rdf-schema#label subscriber
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property

http://www.w3.org/2005/01/wf/flow#creates
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2005/01/wf/flow#Task
http://www.w3.org/2000/01/rdf-schema#label creates
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2000/10/swap/pim/doc#Work
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property

http://www.w3.org/2005/01/wf/flow#initialState
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2005/01/wf/flow#State
http://www.w3.org/2000/01/rdf-schema#label état initial
initial state
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2005/01/wf/flow#Tracker
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment The initial state for a new issue

http://www.w3.org/2005/01/wf/flow#source
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2000/10/swap/pim/doc#Work
http://www.w3.org/2000/01/rdf-schema#label source
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment The source of a transition is the document by which it happened

http://www.w3.org/2005/01/wf/flow#sender
http://www.w3.org/2000/01/rdf-schema#range http://xmlns.com/foaf/0.1/Agent
http://www.w3.org/2000/01/rdf-schema#label from
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2005/01/wf/flow#Message
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property

http://www.w3.org/2005/01/wf/flow#assignee
http://www.w3.org/2000/01/rdf-schema#range http://xmlns.com/foaf/0.1/Agent
http://www.w3.org/2000/01/rdf-schema#label assigned to
http://www.w3.org/2002/07/owl#inverseOf _:1
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment The person or group to whom this has been assigned.

http://www.w3.org/2005/01/wf/flow#requires
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/1999/02/22-rdf-syntax-ns#List
http://www.w3.org/2000/01/rdf-schema#label requires
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2005/01/wf/flow#Transition
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment To be a valid transition, a necessary (but not necessarily sufficuent) condition is that there be recorded these properties for the record

http://www.w3.org/2005/01/wf/flow#NonTerminalState
http://www.w3.org/2000/01/rdf-schema#label non-terminal state
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2000/01/rdf-schema#Class
http://www.w3.org/2002/07/owl#disjointWith http://www.w3.org/2005/01/wf/flow#TerminalState
http://www.w3.org/2000/01/rdf-schema#comment A state from which there are transisions.

http://www.w3.org/2005/01/wf/flow#modifiedBy
http://www.w3.org/2000/01/rdf-schema#range http://xmlns.com/foaf/0.1/Agent
http://www.w3.org/2000/01/rdf-schema#label changed by
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property

http://usefulinc.com/ns/doap#bug-database
http://www.w3.org/2002/07/owl#inverseOf _:2

http://www.w3.org/2005/01/wf/flow#terminalOutput
http://www.w3.org/2000/01/rdf-schema#label terminal output
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment A file showing user interaction from a text terminal or console etc.
http://www.w3.org/2000/01/rdf-schema#subPropertyOf http://www.w3.org/2005/01/wf/flow#attachment

http://www.w3.org/2005/01/wf/flow#date
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2005/01/wf/flow#DateTime

http://www.w3.org/2005/01/wf/flow
http://www.w3.org/2000/01/rdf-schema#comment This ontology defines a very general class (Task) which can used for any kind of bug tracking, issue tracking, to-do-list management, action items, goal depednency, and so on. It captures the state of a task as a subclass, so that subsumption can be used. It captures a discussion thread about a task. It captures subtasks structure if necessary. A "Tracker" defines actual set of states, categories, etc., which a task can be in. The data about the tracker guides the software managing the task. There is some workflow modeling finite state machine terms which are optional for more complex definition of the transitions allowed.
http://purl.org/dc/terms/creator http://www.w3.org/People/Berners-Lee/card#i
http://purl.org/dc/elements/1.1/title Issue Tracking Ontology

_:3
http://www.w3.org/2000/01/rdf-schema#label why

http://www.w3.org/2005/01/wf/flow#Message
http://www.w3.org/2000/01/rdf-schema#label message
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2000/01/rdf-schema#Class

http://www.w3.org/2005/01/wf/flow#attachment
http://www.w3.org/2000/01/rdf-schema#label attachment
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment Something related is attached for information.

http://www.w3.org/2005/01/wf/flow#Transition
http://www.w3.org/2000/01/rdf-schema#label transition
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2000/01/rdf-schema#Class
http://www.w3.org/2000/01/rdf-schema#comment A transition is a change of state of a task. Typical properties include date and/or source (a document causing the transition), and a final state.
http://www.w3.org/2000/01/rdf-schema#subClassOf http://www.w3.org/2005/01/wf/flow#Change

_:2
http://www.w3.org/2000/01/rdf-schema#label project

_:0
http://www.w3.org/2000/01/rdf-schema#label issue

http://www.w3.org/2005/01/wf/flow#Open
http://www.w3.org/2000/01/rdf-schema#label open
ouvert
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2000/01/rdf-schema#Class
http://www.w3.org/2000/01/rdf-schema#comment A task which needs attention. The very crude states of Open and Closed all interoperatbility between different systems if the states for a given application are made subclasses of either Open or Closed. This allows tasks from different systems to be mixed and treatd together with limited but valuable functionality.
http://www.w3.org/2000/01/rdf-schema#subClassOf http://www.w3.org/2005/01/wf/flow#Task

http://www.w3.org/2005/01/wf/flow#TerminalState
http://www.w3.org/2000/01/rdf-schema#label terminal state
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2000/01/rdf-schema#Class
http://www.w3.org/2000/01/rdf-schema#comment A state from which there are no transisions.
http://www.w3.org/2000/01/rdf-schema#subClassOf http://www.w3.org/2005/01/wf/flow#State

http://www.w3.org/2005/01/wf/flow#Change
http://www.w3.org/2000/01/rdf-schema#label change
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2000/01/rdf-schema#Class
http://www.w3.org/2000/01/rdf-schema#comment The universal class of things which change the state of a task. Included now: Creation, Transition. (Maybe in the future more π-calculus constructions such as splitting & merging tasks, and import/export of obligations to a foreign opaque system.)

http://www.w3.org/2005/01/wf/flow#Closed
http://www.w3.org/2000/01/rdf-schema#label fermé
closed
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2000/01/rdf-schema#Class
http://www.w3.org/2000/01/rdf-schema#comment A task which does not neeed attention. It may be closed because has been abandonned or completed, for example.
http://www.w3.org/2000/01/rdf-schema#subClassOf http://www.w3.org/2005/01/wf/flow#Task

_:1
http://www.w3.org/2000/01/rdf-schema#label assignment

http://www.w3.org/2005/01/wf/flow#Product
http://www.w3.org/2000/01/rdf-schema#label product
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2000/01/rdf-schema#Class
http://www.w3.org/2000/01/rdf-schema#comment A product is a task which monitors something which must be produced.
http://www.w3.org/2000/01/rdf-schema#subClassOf http://www.w3.org/2005/01/wf/flow#Task

_:4
http://www.w3.org/1999/02/22-rdf-syntax-ns#first http://www.w3.org/2005/01/wf/flow#Closed
http://www.w3.org/1999/02/22-rdf-syntax-ns#rest http://www.w3.org/1999/02/22-rdf-syntax-ns#nil

http://www.w3.org/2005/01/wf/flow#dependent
http://www.w3.org/2000/01/rdf-schema#range http://www.w3.org/2005/01/wf/flow#Task
http://www.w3.org/2000/01/rdf-schema#label how
http://www.w3.org/2000/01/rdf-schema#domain http://www.w3.org/2005/01/wf/flow#Task
http://www.w3.org/2002/07/owl#inverseOf _:3
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
http://www.w3.org/2000/01/rdf-schema#comment Another task upon which this depends, in the sense that this task cannot be completed without that task being done. You can't use this for dependencies on anything other than other tasks. (Note the US spelling of the URI. In the UK, a dependant is a something which is dependent on somehing else.)

_:5
http://www.w3.org/1999/02/22-rdf-syntax-ns#first http://www.w3.org/2005/01/wf/flow#Open
http://www.w3.org/1999/02/22-rdf-syntax-ns#rest _:4

https://mtp.linked.solutions/wf
http://purl.org/dc/terms/source https://github.com/linked-solutions/prefix.cc-harvest/master
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2002/07/owl#Ontology
http://purl.org/vocab/vann/preferredNamespaceUri http://www.w3.org/2005/01/wf/flow#
http://purl.org/vocab/vann/preferredNamespacePrefix wf
http://rdfs.org/ns/void#triples 194

http://www.w3.org/2005/01/wf/flow#Task
http://www.w3.org/2000/01/rdf-schema#label task
http://www.w3.org/2002/07/owl#disjointUnionOf _:5
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2000/01/rdf-schema#Class
http://www.w3.org/2000/01/rdf-schema#comment Something to be done in a wide sense, an agenda item at a meeting is one example, but any issue, task, action item, goal, product, deliverable, milestone, can such a thing. The requirement for this framework was that it would allow one to customize ontologies for things such as agenda items, action items, working group issues with a spec, w3c Last Call issues, software bugs and administrative requests. In π-calculus, a process. Make your type of issue a subclass of Task.

http://www.w3.org/2005/01/wf/flow#Tracker
http://www.w3.org/2000/01/rdf-schema#label tracker
http://www.w3.org/1999/02/22-rdf-syntax-ns#type http://www.w3.org/2000/01/rdf-schema#Class
http://www.w3.org/2000/01/rdf-schema#comment A set of issues and the constraints on how they evolve. To use this ontology, craete a new tracker. Copy an existing one or make up your own.