0.1.2 Can be used to manage changes (to RDF graphs) by team members. Tag A status object that can be attached to Changes to indicate that they belong to the tag's group. Example Tags include branches and versions. Tag status A resource that can have roles attached to it, e.g. a creator, admin etc. Governed resource Status Change status The types status values for a Change. 1 Change 1 Represents an atomic set of triple changes. The triples are stored as reified triples using the added and deleted properties. Each change should have a creator, which is the agent who submitted the change into the repository. Each change must have a time stamp (dcterms:created) to enable the system to apply changes in the correct order. Statement A replacement of rdf:Statement which leads to problems with some triple stores. Since we do not want to be at the merci of specific triple store features with the native RDF reification vocabulary, we are using our own vocabulary here. This may be revised at a future date, and we will provide automatic update code. role "Abstract" super-property of the roles that a given user (object) can take in the editing of a given resource (subject). manager An editor that has full control over a resource, including the ability to add or remove other users. added Links a change with zero or more added triples, encoded in the binary string rendering. Links a change with zero or more deleted triples, encoded in the binary string rendering. deleted tag Links a Change with zero or more Tags. status The current status of a Change or Tag. May change over its life time, i.e. a change may switch from committed to uncommitted. default tag Can be used to links a UserAccount with a Tag, so that the next time the user logs in, only the changes with matching tag will be activated. Currently only one value is allowed here, to simplify the architecture and improve query performance, but in the future this might be generalized. initial change status Specifies the status that new changes should get when they are added to this repository. Default is teamwork:Uncommitted. If teamwork:Committed is selected, then changes will be written through into the target graph immediately, and the change repository will only serve as a log. Uncommitted changes will just be stored in the repository and may be taken through a reviewing process separately. A viewer that is also allowed to make edits to the resource he is an editor of. editor viewer A user that can also see the change history (and make comments). predicate subject object committed the changes have been written to the gold copy and no further edits are possible. rejected changes will not be written to the gold copy. Only users with editor privilege on the vocabulary or adminstrators of this workspace can change this status. frozen for review the changes are not committed yet to the gold copy, and no further edits are permitted. Only users with editor privilege on the vocabulary or adminstrators of this workspace can change this status. uncommitted changes have not been written (published) to the vocabulary, and further edits are possible. Only users with editor privilege on the vocabulary or adminstrators of this workspace can change this status.