Package de.naturzukunft.rdf4j.vocabulary

Class WF

java.lang.Object
de.naturzukunft.rdf4j.vocabulary.WF
public class WF extends Object
Issue tracking - Workflow application definition ontology Finite state automaton ontology See requirements for tracking tools http://www.w3.org/2005/01/06-tool-req.html Namespace wf Prefix: <http://www.w3.org/2005/01/wf/flow#> Hauschel Fred 2/2021 i got the Ontology from curl --location --request GET 'http://www.w3.org/2005/01/wf/flow' --header 'Accept: application/rdf+xml' And generate this Class with com.github.ansell.rdf4j-schema-generator:schema-generator-maven-plugin:0.4.2 But there was some modification necessary, so i throw the generator project away and keept this manual adjusted Class. The turtle file is located here: /src/main/resources/IssueTrackingWorkflow.ttl Authors 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 dependency, 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.

  • Field Details

    • NAMESPACE

      public static final String NAMESPACE
      <http://www.w3.org/2005/01/wf/flow#>
      See Also:

    • NAMESPACE_IRI

      public static final org.eclipse.rdf4j.model.IRI NAMESPACE_IRI
      <http://www.w3.org/2005/01/wf/flow#>

    • PREFIX

      public static final String PREFIX
      <wf>
      See Also:

    • ACTION_ITEM_STRING

      public static final String ACTION_ITEM_STRING
      action item

      http://www.w3.org/2005/01/wf/flow#ActionItem

      An obligation taken on by a person, typically at a meeting.

      See Also:

    • AFFECTS_STRING

      public static final String AFFECTS_STRING
      affects

      http://www.w3.org/2005/01/wf/flow#affects

      See Also:

    • ALLOWED_TRANSITIONS_STRING

      public static final String ALLOWED_TRANSITIONS_STRING
      allowed transitions

      http://www.w3.org/2005/01/wf/flow#allowedTransitions

      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.)

      See Also:

    • ASIGNEE_CLASS_STRING

      public static final String ASIGNEE_CLASS_STRING
      assignees must be

      http://www.w3.org/2005/01/wf/flow#asigneeClass

      When an issue is assigned, the assignee must be from this class

      See Also:

    • ASSIGNEE_STRING

      public static final String ASSIGNEE_STRING
      assigned to

      http://www.w3.org/2005/01/wf/flow#assignee

      The person or group to whom this has been assigned.

      See Also:

    • ATTACHMENT_STRING

      public static final String ATTACHMENT_STRING
      attachment

      http://www.w3.org/2005/01/wf/flow#attachment

      Something related is attached for information.

      See Also:

    • CHANGE_STRING

      public static final String CHANGE_STRING
      change

      http://www.w3.org/2005/01/wf/flow#Change

      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.)

      See Also:

    • CLOSED_STRING

      public static final String CLOSED_STRING
      closed

      http://www.w3.org/2005/01/wf/flow#Closed

      A task which does not need attention. It may be closed because has been abandoned or completed, for example.

      See Also:

    • CREATES_STRING

      public static final String CREATES_STRING
      creates

      http://www.w3.org/2005/01/wf/flow#creates

      See Also:

    • CREATION_STRING

      public static final String CREATION_STRING
      creation

      http://www.w3.org/2005/01/wf/flow#Creation

      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.

      See Also:

    • DATE_STRING

      public static final String DATE_STRING
      http://www.w3.org/2005/01/wf/flow#date
      See Also:

    • DATE_DUE_STRING

      public static final String DATE_DUE_STRING
      due

      http://www.w3.org/2005/01/wf/flow#dateDue

      The date this task is due.

      See Also:

    • DELIVERABLE_STRING

      public static final String DELIVERABLE_STRING
      deliverable

      http://www.w3.org/2005/01/wf/flow#deliverable

      Something which must be delivered to accomplish this

      See Also:

    • DEPENDENT_STRING

      public static final String DEPENDENT_STRING
      how

      http://www.w3.org/2005/01/wf/flow#dependent

      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.)

      See Also:

    • DESCRIPTION_STRING

      public static final String DESCRIPTION_STRING
      description

      http://www.w3.org/2005/01/wf/flow#description

      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.).

      See Also:

    • FINAL_STRING

      public static final String FINAL_STRING
      to

      http://www.w3.org/2005/01/wf/flow#final

      See Also:

    • GOAL_DESCRIPTION_STRING

      public static final String GOAL_DESCRIPTION_STRING
      goals

      http://www.w3.org/2005/01/wf/flow#goalDescription

      A textual description of the goals of this product, etc.

      See Also:

    • INITIAL_STATE_STRING

      public static final String INITIAL_STATE_STRING
      initial state

      http://www.w3.org/2005/01/wf/flow#initialState

      The initial state for a new issue

      See Also:

    • ISSUE_STRING

      public static final String ISSUE_STRING
      issue

      http://www.w3.org/2005/01/wf/flow#issue

      A transition changes the state of the given issue.

      See Also:

    • ISSUE_CATEGORY_STRING

      public static final String ISSUE_CATEGORY_STRING
      issue category

      http://www.w3.org/2005/01/wf/flow#issueCategory

      Issues may be categorized according to the subclasses of this class

      See Also:

    • ISSUE_CLASS_STRING

      public static final String ISSUE_CLASS_STRING
      all issues must be in

      http://www.w3.org/2005/01/wf/flow#issueClass

      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)

      See Also:

    • MESSAGE_STRING

      public static final String MESSAGE_STRING
      message

      http://www.w3.org/2005/01/wf/flow#Message

      See Also:

    • MESSAGE_PROP_STRING

      public static final String MESSAGE_PROP_STRING
      message

      http://www.w3.org/2005/01/wf/flow#message

      A message about this. Attached for information.

      See Also:

    • MODIFIED_BY_STRING

      public static final String MODIFIED_BY_STRING
      changed by

      http://www.w3.org/2005/01/wf/flow#modifiedBy

      See Also:

    • NON_TERMINAL_STATE_STRING

      public static final String NON_TERMINAL_STATE_STRING
      non-terminal state

      http://www.w3.org/2005/01/wf/flow#NonTerminalState

      A state from which there are transitions.

      See Also:

    • OPEN_STRING

      public static final String OPEN_STRING
      open

      http://www.w3.org/2005/01/wf/flow#Open

      A task which needs attention. The very crude states of Open and Closed all interoperability 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 treated together with limited but valuable functionality.

      See Also:

    • PRODUCT_STRING

      public static final String PRODUCT_STRING
      product

      http://www.w3.org/2005/01/wf/flow#Product

      A product is a task which monitors something which must be produced.

      See Also:

    • RECIPENT_STRING

      public static final String RECIPENT_STRING
      to

      http://www.w3.org/2005/01/wf/flow#recipent

      See Also:

    • REQUIRES_STRING

      public static final String REQUIRES_STRING
      requires

      http://www.w3.org/2005/01/wf/flow#requires

      To be a valid transition, a necessary (but not necessarily sufficuent) condition is that there be recorded these properties for the record

      See Also:

    • SCREEN_SHOT_STRING

      public static final String SCREEN_SHOT_STRING
      screen shot

      http://www.w3.org/2005/01/wf/flow#screenShot

      An image taken by capturing the state of a computer screen, for example to demonstrate a problem

      See Also:

    • SENDER_STRING

      public static final String SENDER_STRING
      from

      http://www.w3.org/2005/01/wf/flow#sender

      See Also:

    • SOURCE_STRING

      public static final String SOURCE_STRING
      source

      http://www.w3.org/2005/01/wf/flow#source

      The source of a transition is the document by which it happened

      See Also:

    • STATE_STORE_STRING

      public static final String STATE_STORE_STRING
      state store

      http://www.w3.org/2005/01/wf/flow#stateStore

      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.

      See Also:

    • SUBSCRIBER_STRING

      public static final String SUBSCRIBER_STRING
      subscriber

      http://www.w3.org/2005/01/wf/flow#subscriber

      See Also:

    • SUCCESS_CRITERIA_STRING

      public static final String SUCCESS_CRITERIA_STRING
      success criteria

      http://www.w3.org/2005/01/wf/flow#successCriteria

      A textual description of the successs critera. How when we know this is done?

      See Also:

    • TASK_STRING

      public static final String TASK_STRING
      task

      http://www.w3.org/2005/01/wf/flow#Task

      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.

      See Also:

    • TASK_PROP_STRING

      public static final String TASK_PROP_STRING
      task

      http://www.w3.org/2005/01/wf/flow#task

      See Also:

    • TERMINAL_OUTPUT_STRING

      public static final String TERMINAL_OUTPUT_STRING
      terminal output

      http://www.w3.org/2005/01/wf/flow#terminalOutput

      A file showing user interaction from a text terminal or console etc.

      See Also:

    • TERMINAL_STATE_STRING

      public static final String TERMINAL_STATE_STRING
      terminal state

      http://www.w3.org/2005/01/wf/flow#TerminalState

      A state from which there are no transitions.

      See Also:

    • TEST_DATA_STRING

      public static final String TEST_DATA_STRING
      test data

      http://www.w3.org/2005/01/wf/flow#testData

      A file which can be used as inpiut to a test or to demonstrate a problem.

      See Also:

    • TRACKER_STRING

      public static final String TRACKER_STRING
      tracker

      http://www.w3.org/2005/01/wf/flow#Tracker

      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.

      See Also:

    • TRACKER_PROP_STRING

      public static final String TRACKER_PROP_STRING
      tracker

      http://www.w3.org/2005/01/wf/flow#tracker

      See Also:

    • TRANSACTION_STORE_STRING

      public static final String TRANSACTION_STORE_STRING
      transaction store

      http://www.w3.org/2005/01/wf/flow#transactionStore

      An appendable document. Transactions and messsages can be written into here

      See Also:

    • TRANSITION_STRING

      public static final String TRANSITION_STRING
      transition

      http://www.w3.org/2005/01/wf/flow#Transition

      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.

      See Also:

    • ACTION_ITEM_LOCALNAME

      public static final String ACTION_ITEM_LOCALNAME
      action item

      http://www.w3.org/2005/01/wf/flow#ActionItem

      An obligation taken on by a person, typically at a meeting.

      See Also:

    • AFFECTS_LOCALNAME

      public static final String AFFECTS_LOCALNAME
      affects

      http://www.w3.org/2005/01/wf/flow#affects

      See Also:

    • ALLOWED_TRANSITIONS_LOCALNAME

      public static final String ALLOWED_TRANSITIONS_LOCALNAME
      allowed transitions

      http://www.w3.org/2005/01/wf/flow#allowedTransitions

      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.)

      See Also:

    • ASIGNEE_CLASS_LOCALNAME

      public static final String ASIGNEE_CLASS_LOCALNAME
      assignees must be

      http://www.w3.org/2005/01/wf/flow#asigneeClass

      When an issue is assigned, the assignee must be from this class

      See Also:

    • ASSIGNEE_LOCALNAME

      public static final String ASSIGNEE_LOCALNAME
      assigned to

      http://www.w3.org/2005/01/wf/flow#assignee

      The person or group to whom this has been assigned.

      See Also:

    • ATTACHMENT_LOCALNAME

      public static final String ATTACHMENT_LOCALNAME
      attachment

      http://www.w3.org/2005/01/wf/flow#attachment

      Something related is attached for information.

      See Also:

    • CHANGE_LOCALNAME

      public static final String CHANGE_LOCALNAME
      change

      http://www.w3.org/2005/01/wf/flow#Change

      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.)

      See Also:

    • CLOSED_LOCALNAME

      public static final String CLOSED_LOCALNAME
      closed

      http://www.w3.org/2005/01/wf/flow#Closed

      A task which does not need attention. It may be closed because has been abandoned or completed, for example.

      See Also:

    • CREATES_LOCALNAME

      public static final String CREATES_LOCALNAME
      creates

      http://www.w3.org/2005/01/wf/flow#creates

      See Also:

    • CREATION_LOCALNAME

      public static final String CREATION_LOCALNAME
      creation

      http://www.w3.org/2005/01/wf/flow#Creation

      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.

      See Also:

    • DATE_LOCALNAME

      public static final String DATE_LOCALNAME
      http://www.w3.org/2005/01/wf/flow#date
      See Also:

    • DATE_DUE_LOCALNAME

      public static final String DATE_DUE_LOCALNAME
      due

      http://www.w3.org/2005/01/wf/flow#dateDue

      The date this task is due.

      See Also:

    • DELIVERABLE_LOCALNAME

      public static final String DELIVERABLE_LOCALNAME
      deliverable

      http://www.w3.org/2005/01/wf/flow#deliverable

      Something which must be delivered to accomplish this

      See Also:

    • DEPENDENT_LOCALNAME

      public static final String DEPENDENT_LOCALNAME
      how

      http://www.w3.org/2005/01/wf/flow#dependent

      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.)

      See Also:

    • DESCRIPTION_LOCALNAME

      public static final String DESCRIPTION_LOCALNAME
      description

      http://www.w3.org/2005/01/wf/flow#description

      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.).

      See Also:

    • FINAL_LOCALNAME

      public static final String FINAL_LOCALNAME
      to

      http://www.w3.org/2005/01/wf/flow#final

      See Also:

    • GOAL_DESCRIPTION_LOCALNAME

      public static final String GOAL_DESCRIPTION_LOCALNAME
      goals

      http://www.w3.org/2005/01/wf/flow#goalDescription

      A textual description of the goals of this product, etc.

      See Also:

    • INITIAL_STATE_LOCALNAME

      public static final String INITIAL_STATE_LOCALNAME
      initial state

      http://www.w3.org/2005/01/wf/flow#initialState

      The initial state for a new issue

      See Also:

    • ISSUE_LOCALNAME

      public static final String ISSUE_LOCALNAME
      issue

      http://www.w3.org/2005/01/wf/flow#issue

      A transition changes the state of the given issue.

      See Also:

    • ISSUE_CATEGORY_LOCALNAME

      public static final String ISSUE_CATEGORY_LOCALNAME
      issue category

      http://www.w3.org/2005/01/wf/flow#issueCategory

      Issues may be categorized according to the subclasses of this class

      See Also:

    • ISSUE_CLASS_LOCALNAME

      public static final String ISSUE_CLASS_LOCALNAME
      all issues must be in

      http://www.w3.org/2005/01/wf/flow#issueClass

      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)

      See Also:

    • MESSAGE_LOCALNAME

      public static final String MESSAGE_LOCALNAME
      message

      http://www.w3.org/2005/01/wf/flow#Message

      See Also:

    • MESSAGE_PROP_LOCALNAME

      public static final String MESSAGE_PROP_LOCALNAME
      message

      http://www.w3.org/2005/01/wf/flow#message

      A message about this. Attached for information.

      See Also:

    • MODIFIED_BY_LOCALNAME

      public static final String MODIFIED_BY_LOCALNAME
      changed by

      http://www.w3.org/2005/01/wf/flow#modifiedBy

      See Also:

    • NON_TERMINAL_STATE_LOCALNAME

      public static final String NON_TERMINAL_STATE_LOCALNAME
      non-terminal state

      http://www.w3.org/2005/01/wf/flow#NonTerminalState

      A state from which there are transitions.

      See Also:

    • OPEN_LOCALNAME

      public static final String OPEN_LOCALNAME
      open

      http://www.w3.org/2005/01/wf/flow#Open

      A task which needs attention. The very crude states of Open and Closed all interoperability 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 treated together with limited but valuable functionality.

      See Also:

    • PRODUCT_LOCALNAME

      public static final String PRODUCT_LOCALNAME
      product

      http://www.w3.org/2005/01/wf/flow#Product

      A product is a task which monitors something which must be produced.

      See Also:

    • RECIPENT_LOCALNAME

      public static final String RECIPENT_LOCALNAME
      to

      http://www.w3.org/2005/01/wf/flow#recipent

      See Also:

    • REQUIRES_LOCALNAME

      public static final String REQUIRES_LOCALNAME
      requires

      http://www.w3.org/2005/01/wf/flow#requires

      To be a valid transition, a necessary (but not necessarily sufficuent) condition is that there be recorded these properties for the record

      See Also:

    • SCREEN_SHOT_LOCALNAME

      public static final String SCREEN_SHOT_LOCALNAME
      screen shot

      http://www.w3.org/2005/01/wf/flow#screenShot

      An image taken by capturing the state of a computer screen, for example to demonstrate a problem

      See Also:

    • SENDER_LOCALNAME

      public static final String SENDER_LOCALNAME
      from

      http://www.w3.org/2005/01/wf/flow#sender

      See Also:

    • SOURCE_LOCALNAME

      public static final String SOURCE_LOCALNAME
      source

      http://www.w3.org/2005/01/wf/flow#source

      The source of a transition is the document by which it happened

      See Also:

    • STATE_STORE_LOCALNAME

      public static final String STATE_STORE_LOCALNAME
      state store

      http://www.w3.org/2005/01/wf/flow#stateStore

      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.

      See Also:

    • SUBSCRIBER_LOCALNAME

      public static final String SUBSCRIBER_LOCALNAME
      subscriber

      http://www.w3.org/2005/01/wf/flow#subscriber

      See Also:

    • SUCCESS_CRITERIA_LOCALNAME

      public static final String SUCCESS_CRITERIA_LOCALNAME
      success criteria

      http://www.w3.org/2005/01/wf/flow#successCriteria

      A textual description of the successs critera. How when we know this is done?

      See Also:

    • TASK_LOCALNAME

      public static final String TASK_LOCALNAME
      task

      http://www.w3.org/2005/01/wf/flow#Task

      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.

      See Also:

    • TASK_PROP_LOCALNAME

      public static final String TASK_PROP_LOCALNAME
      task

      http://www.w3.org/2005/01/wf/flow#task

      See Also:

    • TERMINAL_OUTPUT_LOCALNAME

      public static final String TERMINAL_OUTPUT_LOCALNAME
      terminal output

      http://www.w3.org/2005/01/wf/flow#terminalOutput

      A file showing user interaction from a text terminal or console etc.

      See Also:

    • TERMINAL_STATE_LOCALNAME

      public static final String TERMINAL_STATE_LOCALNAME
      terminal state

      http://www.w3.org/2005/01/wf/flow#TerminalState

      A state from which there are no transitions.

      See Also:

    • TEST_DATA_LOCALNAME

      public static final String TEST_DATA_LOCALNAME
      test data

      http://www.w3.org/2005/01/wf/flow#testData

      A file which can be used as inpiut to a test or to demonstrate a problem.

      See Also:

    • TRACKER_LOCALNAME

      public static final String TRACKER_LOCALNAME
      tracker

      http://www.w3.org/2005/01/wf/flow#Tracker

      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.

      See Also:

    • TRACKER_PROP_LOCALNAME

      public static final String TRACKER_PROP_LOCALNAME
      tracker

      http://www.w3.org/2005/01/wf/flow#tracker

      See Also:

    • TRANSACTION_STORE_LOCALNAME

      public static final String TRANSACTION_STORE_LOCALNAME
      transaction store

      http://www.w3.org/2005/01/wf/flow#transactionStore

      An appendable document. Transactions and messsages can be written into here

      See Also:

    • TRANSITION_LOCALNAME

      public static final String TRANSITION_LOCALNAME
      transition

      http://www.w3.org/2005/01/wf/flow#Transition

      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.

      See Also:

    • ACTION_ITEM

      public static final org.eclipse.rdf4j.model.IRI ACTION_ITEM
      action item

      http://www.w3.org/2005/01/wf/flow#ActionItem

      An obligation taken on by a person, typically at a meeting.

      See Also:

    • AFFECTS

      public static final org.eclipse.rdf4j.model.IRI AFFECTS
      affects

      http://www.w3.org/2005/01/wf/flow#affects

      See Also:

    • ALLOWED_TRANSITIONS

      public static final org.eclipse.rdf4j.model.IRI ALLOWED_TRANSITIONS
      allowed transitions

      http://www.w3.org/2005/01/wf/flow#allowedTransitions

      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.)

      See Also:

    • ASIGNEE_CLASS

      public static final org.eclipse.rdf4j.model.IRI ASIGNEE_CLASS
      assignees must be

      http://www.w3.org/2005/01/wf/flow#asigneeClass

      When an issue is assigned, the assignee must be from this class

      See Also:

    • ASSIGNEE

      public static final org.eclipse.rdf4j.model.IRI ASSIGNEE
      assigned to

      http://www.w3.org/2005/01/wf/flow#assignee

      The person or group to whom this has been assigned.

      See Also:

    • ATTACHMENT

      public static final org.eclipse.rdf4j.model.IRI ATTACHMENT
      attachment

      http://www.w3.org/2005/01/wf/flow#attachment

      Something related is attached for information.

      See Also:

    • CHANGE

      public static final org.eclipse.rdf4j.model.IRI CHANGE
      change

      http://www.w3.org/2005/01/wf/flow#Change

      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.)

      See Also:

    • CLOSED

      public static final org.eclipse.rdf4j.model.IRI CLOSED
      closed

      http://www.w3.org/2005/01/wf/flow#Closed

      A task which does not need attention. It may be closed because has been abandoned or completed, for example.

      See Also:

    • CREATES

      public static final org.eclipse.rdf4j.model.IRI CREATES
      creates

      http://www.w3.org/2005/01/wf/flow#creates

      See Also:

    • CREATION

      public static final org.eclipse.rdf4j.model.IRI CREATION
      creation

      http://www.w3.org/2005/01/wf/flow#Creation

      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.

      See Also:

    • DATE

      public static final org.eclipse.rdf4j.model.IRI DATE
      http://www.w3.org/2005/01/wf/flow#date
      See Also:

    • DATE_DUE

      public static final org.eclipse.rdf4j.model.IRI DATE_DUE
      due

      http://www.w3.org/2005/01/wf/flow#dateDue

      The date this task is due.

      See Also:

    • DELIVERABLE

      public static final org.eclipse.rdf4j.model.IRI DELIVERABLE
      deliverable

      http://www.w3.org/2005/01/wf/flow#deliverable

      Something which must be delivered to accomplish this

      See Also:

    • DEPENDENT

      public static final org.eclipse.rdf4j.model.IRI DEPENDENT
      how

      http://www.w3.org/2005/01/wf/flow#dependent

      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.)

      See Also:

    • DESCRIPTION

      public static final org.eclipse.rdf4j.model.IRI DESCRIPTION
      description

      http://www.w3.org/2005/01/wf/flow#description

      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.).

      See Also:

    • FINAL

      public static final org.eclipse.rdf4j.model.IRI FINAL
      to

      http://www.w3.org/2005/01/wf/flow#final

      See Also:

    • GOAL_DESCRIPTION

      public static final org.eclipse.rdf4j.model.IRI GOAL_DESCRIPTION
      goals

      http://www.w3.org/2005/01/wf/flow#goalDescription

      A textual description of the goals of this product, etc.

      See Also:

    • INITIAL_STATE

      public static final org.eclipse.rdf4j.model.IRI INITIAL_STATE
      initial state

      http://www.w3.org/2005/01/wf/flow#initialState

      The initial state for a new issue

      See Also:

    • ISSUE

      public static final org.eclipse.rdf4j.model.IRI ISSUE
      issue

      http://www.w3.org/2005/01/wf/flow#issue

      A transition changes the state of the given issue.

      See Also:

    • ISSUE_CATEGORY

      public static final org.eclipse.rdf4j.model.IRI ISSUE_CATEGORY
      issue category

      http://www.w3.org/2005/01/wf/flow#issueCategory

      Issues may be categorized according to the subclasses of this class

      See Also:

    • ISSUE_CLASS

      public static final org.eclipse.rdf4j.model.IRI ISSUE_CLASS
      all issues must be in

      http://www.w3.org/2005/01/wf/flow#issueClass

      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)

      See Also:

    • MESSAGE

      public static final org.eclipse.rdf4j.model.IRI MESSAGE
      message

      http://www.w3.org/2005/01/wf/flow#Message

      See Also:

    • MESSAGE_PROP

      public static final org.eclipse.rdf4j.model.IRI MESSAGE_PROP
      message

      http://www.w3.org/2005/01/wf/flow#message

      A message about this. Attached for information.

      See Also:

    • MODIFIED_BY

      public static final org.eclipse.rdf4j.model.IRI MODIFIED_BY
      changed by

      http://www.w3.org/2005/01/wf/flow#modifiedBy

      See Also:

    • NON_TERMINAL_STATE

      public static final org.eclipse.rdf4j.model.IRI NON_TERMINAL_STATE
      non-terminal state

      http://www.w3.org/2005/01/wf/flow#NonTerminalState

      A state from which there are transitions.

      See Also:

    • OPEN

      public static final org.eclipse.rdf4j.model.IRI OPEN
      open

      http://www.w3.org/2005/01/wf/flow#Open

      A task which needs attention. The very crude states of Open and Closed all interoperability 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 treated together with limited but valuable functionality.

      See Also:

    • PRODUCT

      public static final org.eclipse.rdf4j.model.IRI PRODUCT
      product

      http://www.w3.org/2005/01/wf/flow#Product

      A product is a task which monitors something which must be produced.

      See Also:

    • RECIPENT

      public static final org.eclipse.rdf4j.model.IRI RECIPENT
      to

      http://www.w3.org/2005/01/wf/flow#recipent

      See Also:

    • REQUIRES

      public static final org.eclipse.rdf4j.model.IRI REQUIRES
      requires

      http://www.w3.org/2005/01/wf/flow#requires

      To be a valid transition, a necessary (but not necessarily sufficuent) condition is that there be recorded these properties for the record

      See Also:

    • SCREEN_SHOT

      public static final org.eclipse.rdf4j.model.IRI SCREEN_SHOT
      screen shot

      http://www.w3.org/2005/01/wf/flow#screenShot

      An image taken by capturing the state of a computer screen, for example to demonstrate a problem

      See Also:

    • SENDER

      public static final org.eclipse.rdf4j.model.IRI SENDER
      from

      http://www.w3.org/2005/01/wf/flow#sender

      See Also:

    • SOURCE

      public static final org.eclipse.rdf4j.model.IRI SOURCE
      source

      http://www.w3.org/2005/01/wf/flow#source

      The source of a transition is the document by which it happened

      See Also:

    • STATE_STORE

      public static final org.eclipse.rdf4j.model.IRI STATE_STORE
      state store

      http://www.w3.org/2005/01/wf/flow#stateStore

      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.

      See Also:

    • SUBSCRIBER

      public static final org.eclipse.rdf4j.model.IRI SUBSCRIBER
      subscriber

      http://www.w3.org/2005/01/wf/flow#subscriber

      See Also:

    • SUCCESS_CRITERIA

      public static final org.eclipse.rdf4j.model.IRI SUCCESS_CRITERIA
      success criteria

      http://www.w3.org/2005/01/wf/flow#successCriteria

      A textual description of the successs critera. How when we know this is done?

      See Also:

    • TASK

      public static final org.eclipse.rdf4j.model.IRI TASK
      task

      http://www.w3.org/2005/01/wf/flow#Task

      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.

      See Also:

    • TASK_PROP

      public static final org.eclipse.rdf4j.model.IRI TASK_PROP
      task

      http://www.w3.org/2005/01/wf/flow#task

      See Also:

    • TERMINAL_OUTPUT

      public static final org.eclipse.rdf4j.model.IRI TERMINAL_OUTPUT
      terminal output

      http://www.w3.org/2005/01/wf/flow#terminalOutput

      A file showing user interaction from a text terminal or console etc.

      See Also:

    • TERMINAL_STATE

      public static final org.eclipse.rdf4j.model.IRI TERMINAL_STATE
      terminal state

      http://www.w3.org/2005/01/wf/flow#TerminalState

      A state from which there are no transitions.

      See Also:

    • TEST_DATA

      public static final org.eclipse.rdf4j.model.IRI TEST_DATA
      test data

      http://www.w3.org/2005/01/wf/flow#testData

      A file which can be used as inpiut to a test or to demonstrate a problem.

      See Also:

    • TRACKER

      public static final org.eclipse.rdf4j.model.IRI TRACKER
      tracker

      http://www.w3.org/2005/01/wf/flow#Tracker

      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.

      See Also:

    • TRACKER_PROP

      public static final org.eclipse.rdf4j.model.IRI TRACKER_PROP
      tracker

      http://www.w3.org/2005/01/wf/flow#tracker

      See Also:

    • TRANSACTION_STORE

      public static final org.eclipse.rdf4j.model.IRI TRANSACTION_STORE
      transaction store

      http://www.w3.org/2005/01/wf/flow#transactionStore

      An appendable document. Transactions and messsages can be written into here

      See Also:

    • TRANSITION

      public static final org.eclipse.rdf4j.model.IRI TRANSITION
      transition

      http://www.w3.org/2005/01/wf/flow#Transition

      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.

      See Also:

  • Constructor Details

    • WF

      public WF()