all issues must be in
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)
allowed transitions
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.)
- 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.)
- Domain
- State
- Label
- allowed transitions
- Range
- List
- Comment
- The person or group to whom this has been assigned.
- InverseOf
-
assignment
- Label
- assignment
- Label
- assigned to
- Range
- Agent
- Comment
- Something related is attached for information.
- Label
- attachment
- InverseOf
-
project
- Label
- enproject
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.)
- 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.)
- Label
- change
- Label
- changed by
- Range
- Agent
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.
- 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.
- Label
- creation
- SubClassOf
- change
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.).
- 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.).
- Label
- description
how
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.)
- 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.)
- Domain
- task
- InverseOf
-
why
- Label
- why
- Label
- how
- Range
- task
Issue Tracking Ontology
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.
- 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.
- Creator
- i
- Title
- Issue Tracking Ontology
- Comment
- A message about this. Attached for information.
- Label
- enmessage
- SubPropertyOf
- attachment
- Comment
- A state from which there are transitions.
- DisjointWith
- terminal state
- Label
- non-terminal state
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.
- BackgroundColor
- #d6f5d6
- Comment
- 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.
- Label
- enopen
- SubClassOf
- task
requires
To be a valid transition, a necessary (but not necessarily sufficuent) condition is that there be recorded these properties for the record
- Comment
- To be a valid transition, a necessary (but not necessarily sufficuent) condition is that there be recorded these properties for the record
- Domain
- transition
- Label
- requires
- Range
- List
screen shot
An image taken by capturing the state of a computer screen, for example to demonstrate a problem
- Comment
- An image taken by capturing the state of a computer screen, for example to demonstrate a problem
- Label
- enscreen shot
- SubPropertyOf
- attachment
state store
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.
- Label
- subscriber
- Range
- Agent
success criteria
A textual description of the successs critera. How when we know this is done?
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.
- 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.
- DisjointUnionOf
- Label
- entask
- Comment
- A file showing user interaction from a text terminal or console etc.
- Label
- enterminal output
- SubPropertyOf
- attachment
- Comment
- A state from which there are no transitions.
- Label
- terminal state
- SubClassOf
- State
- Comment
- A file which can be used as inpiut to a test or to demonstrate a problem.
- Label
- entest data
- SubPropertyOf
- attachment
- Domain
- transition
- Label
- to
- Range
- State
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.
- 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.
- Label
- tracker
transaction store
An appendable document. Transactions and messsages can be written into here
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.
- 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.
- Label
- transition
- SubClassOf
- change