<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XML Spy v3.5 NT (http://www.xmlspy.com) by Carl Lagoze (Cornell University) -->
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
	<rdfs:Class rdf:ID="Entity">
		<rdfs:comment>The primitive category having no differentiae. </rdfs:comment>
	</rdfs:Class>
	<rdfs:Class rdf:ID="Temporality">
		<rdfs:comment>A primitive ontology category for sub-classing categories of entities that provide time existential contexts.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="Entity"/>
	</rdfs:Class>
	<rdfs:Class rdf:ID="Actuality">
		<rdfs:comment>A primitive ontology category for sub-classing categories of entities that have a tangible existence in some world view.  Actualities as identities and properties associated with those properties have a duality as continuants - entities whose identity as a set of properties/characteristics are time independent relative to the world view of a model - and occurrents - entities whose identity as a set of properties/characteristics are local to states/contexts in a model.  The hasInstance and inState properties are means of co-relating an occurrent facet of an Actuality and its continuent facet and of associating the occurrent facet with a specific state.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="Entity"/>
	</rdfs:Class>
	<rdfs:Class rdf:ID="Abstraction">
		<rdfs:comment>A primitive ontology category for sub-classing categories of entities that are pure information or concepts (stands in contrast to the Actuality category).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="Entity"/>
	</rdfs:Class>
	<rdfs:Class rdf:ID="Artifact">
		<rdfs:comment>A type of Actuality that is the tangible realization of some pre-conceived Abstraction - a prototypical example is intellectual content.  The primary distinguishing characteristics of Artifacts is that they can be manifested in a number of ways and copied - for example the book "Hamlet" is an Artifact (of the Abstraction Hamlet) since it is one of many possible Actualities.  This contrasts to the Actuality William Shakespeare who admittedly may have been pre-conceived by his parents but can not be manifested in various ways.  Similarly a historical museum object such as a dinosaur bone is an Actuality but not an Artifact.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="Actuality"/>
	</rdfs:Class>
	<rdfs:Class rdf:ID="Event">
		<rdfs:comment>An Event marks a change in State - a time snapshot in a process model. It corresponds to a transition in a Petri Net or an event in a flow-chart.  Its status as a transition between two States is codified by its  association via properites to two States, one State connected via the isInput property to the Event and the other State connected via the isOutput to the Event.  The granularity of the snapshot is variable - for example some Events are truly an instant (a point in time).  However, an Event may have coarser granularity such as span of time during which some state change was undertaken (for example, the painting of the Sistine Chapen Ceiling). The granularity of the snapshot is associated with the Event via a single atTIme property.  Events provide an existential context for associated Actions or verbs, which provide anchors for agents and associated activities that contribute to the state change.  This differentiates them from States, which provide the existential context for occurrent facets of Actualities.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="Temporality"/>
	</rdfs:Class>
	<rdfs:Class rdf:ID="State">
		<rdfs:comment>A State is a context for making assertions about Actualities.  A State corresponds to the concept of a place in a Petri Net or a state in a finite-state machine.  A State stands in contrast to an Event, meaning that Events mark snapshots of change (possibly influenced by some Agent) whereas States mark periods of stability establishing a context for properties to be asserted for Actualities.  Another way of saying this is States provide a context for adjectives (properties) on Actualities, where Events provide a context for verbs (Actions) by Agents.   The time certainty for a State is implicitly within the time contexts for the events that enclose it (i.e. a State can serve as the isInput of one Event and the isOutput of another).  However, the time certainty can be be explicitly stated via a atTime property on the State.  The purpose of this is to make the model as closed as possible - where the time certainty of Events and States is known. </rdfs:comment>
		<rdfs:subClassOf rdf:resource="Temporality"/>
	</rdfs:Class>
	<rdfs:Class rdf:ID="Action">
		<rdfs:comment>An activity or verb performed by some Agent or Agents in the context of an Event.  Actions may involve an Actuality, which may be in its occurent or continuant facet, and may have result that is another Actuality, which always must be in its occurrent facet.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="Temporality"/>
	</rdfs:Class>
	<rdfs:Class rdf:ID="Agent">
		<rdfs:comment>A subject of an Action.  Agents may be persons, instruments, organizations, etc.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="Actuality"/>
	</rdfs:Class>
	<rdfs:Class rdf:ID="Work">
		<rdfs:comment>An Abstraction that is intellectual property in the IFLA FRBR sense. A Work can not exist in a model in isolation, an Abstraction is only revealed when it has been actualized in some Manifestation. </rdfs:comment>
		<rdfs:subClassOf rdf:resource="Abstraction"/>
	</rdfs:Class>
	<rdfs:Class rdf:ID="Manifestation">
		<rdfs:comment>A form of an Artifact that stands as the sensible realization of a Work.  Works  and Manifestations stand in a one to many relationship. The isRealized property associates a Work with its Manifestation(s). Associating several Manifestations with a Work through the isRealized property defines those Manifestations as members of a (fuzzy) equivalence class implicitly identified by the Work.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="Artifact"/>
	</rdfs:Class>
	<rdfs:Class rdf:ID="Item">
		<rdfs:comment>A form of an Artifact used to establish a set of identical copies.  Manifestations and Items stand in a one to many relationship.  The isCopied property associates a Manifestation with its Items.  Associating several Items with a Manifestation through the isCopied property defines those Items as members of an exact equivalence class.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="Artifact"/>
	</rdfs:Class>
	<rdf:Property rdf:ID="hasInput">
		<rdfs:comment>Binds a State and the Actualities within its context as existing before an Event.</rdfs:comment>
		<rdfs:domain rdf:resource="Event"/>
		<rdfs:range rdf:resource="State"/>
	</rdf:Property>
	<rdf:Property rdf:ID="hasOutput">
		<rdfs:comment>Binds a State and the Actualities within its context as existing after an Event.  There is no explicit implication of causality between the Event and Actualities existing in the State that is the value of the hasOutput property.  Causality between Events or Actions in Events and Actualities is established through the hasResult property and its sub-properties.</rdfs:comment>
		<rdfs:domain rdf:resource="Event"/>
		<rdfs:range rdf:resource="State"/>
	</rdf:Property>
	<rdf:Property rdf:ID="contains">
		<rdfs:comment>Establishes a relationship between a State and an occurrent facet of an Actuality (reverse of inState).</rdfs:comment>
		<rdfs:domain rdf:resource="State"/>
		<rdfs:range rdf:resource="Actuality"/>
	</rdf:Property>
	<rdf:Property rdf:ID="inState">
		<rdfs:comment>Establishes an Actuality as an occurrent, which means that its property set exists within the context of State that is associated as the value of this property (reverse of contains).</rdfs:comment>
		<rdfs:domain rdf:resource="Actuality"/>
		<rdfs:range rdf:resource="State"/>
	</rdf:Property>
	<rdf:Property rdf:ID="hasInstance">
		<rdfs:comment>Binds the continuent facet of Binds the continuent facet of an Actuality to its occurrent facet.  The Actuality that is the value of this property must itself have an inState property to establish its statefulness. Effectively the properties of the continuent facet (the subject of the hasInstance property) are constant in the world view of the model and the properties of the occurrent facet (the value of the hasInstance property) are in the scope if its associated State. (reverse of instanceOf).</rdfs:comment>
		<rdfs:domain rdf:resource="Actuality"/>
		<rdfs:range rdf:resource="Actuality"/>
	</rdf:Property>
	<rdf:Property rdf:ID="instanceOf">
		<rdfs:comment>Establishes the relationship between an occurrent facet and a continuant facet of an Actuality (reverse of hasInstance).</rdfs:comment>
		<rdfs:domain rdf:resource="Actuality"/>
		<rdfs:range rdf:resource="Actuality"/>
	</rdf:Property>
	<rdf:Property rdf:ID="hasRealization">
		<rdfs:comment>inds a Manifestation within the conceptual umbrella of a Work.  A Work may have several hasRealization properties, which establishes a fuzzy equivalence set among manifestations, implicitly stating that the properties of the subject Work are shared across the object Manifestation(s).  </rdfs:comment>
		<rdfs:domain rdf:resource="Work"/>
		<rdfs:range rdf:resource="Manifestation"/>
	</rdf:Property>
	<rdf:Property rdf:ID="hasCopy">
		<rdfs:comment>Binds an Item as one of several copies of a Manifestation.  A   Manifestation may have several isCopied properties, which establishes an exact equivalence set among Manifestations, implicitly stating that the properties of the subject Manifestation are shared across the object Item(s).   </rdfs:comment>
		<rdfs:domain rdf:resource="Manifestation"/>
		<rdfs:range rdf:resource="Item"/>
	</rdf:Property>
	<rdf:Property rdf:ID="involves">
		<rdfs:comment>Expresses the involvement of an Actuality in the performance of an Action (in the context of an Event).  There is no implication of transformation in this use.      </rdfs:comment>
		<rdfs:domain rdf:resource="Action"/>
		<rdfs:domain rdf:resource="Event"/>
		<rdfs:range rdf:resource="Actuality"/>
	</rdf:Property>
	<rdf:Property rdf:ID="hasPatient">
		<rdfs:comment>Strengthens the notion of involves to the classic patient sense stating that the Actuality that is the value is transformed by the Action.    </rdfs:comment>
		<rdfs:domain rdf:resource="Event"/>
		<rdfs:domain rdf:resource="Action"/>
		<rdfs:range rdf:resource="Actuality"/>
		<rdfs:subPropertyOf rdf:resource="involves"/>
	</rdf:Property>
	<rdf:Property rdf:ID="usesTool">
		<rdfs:comment>A specialization of involves that in effect weakens the notion of involvement of the Actuality in the Action - e.g., it is used but not transformed.</rdfs:comment>
		<rdfs:domain rdf:resource="Event"/>
		<rdfs:domain rdf:resource="Action"/>
		<rdfs:range rdf:resource="Actuality"/>
		<rdfs:subPropertyOf rdf:resource="inPresence"/>
	</rdf:Property>
	<rdf:Property rdf:ID="hasResult">
		<rdfs:comment>Expresses the result of an Actuality, which always must be in an occurent facet, in the performance of an Action (in the context of an Event).      </rdfs:comment>
		<rdfs:domain rdf:resource="Action"/>
		<rdfs:domain rdf:resource="Event"/>
		<rdfs:range rdf:resource="Actuality"/>
	</rdf:Property>
	<rdf:Property rdf:ID="destroys">
		<rdfs:comment>A specialization of hasPatient that indicates that the value Actuality ceases to exist in State(s) that are output of the Event.  Any Actuality that is not explicitly destroyed can be assumed to exist in subsequent States even though it might not be explicitly represented.</rdfs:comment>
		<rdfs:domain rdf:resource="Event"/>
		<rdfs:domain rdf:resource="Action"/>
		<rdfs:range rdf:resource="Actuality"/>
		<rdfs:subPropertyOf rdf:resource="hasPatient"/>
	</rdf:Property>
	<rdf:Property rdf:ID="creates">
		<rdfs:comment>pecializes hasResult to mean the coming into existence of the Actuality that is the value of this property.  This means that the Actuality can be assumed to not exist in States prior to the one in which the created instance of the Actuality appears.</rdfs:comment>
		<rdfs:domain rdf:resource="Action"/>
		<rdfs:domain rdf:resource="Event"/>
		<rdfs:range rdf:resource="Actuality"/>
		<rdfs:subPropertyOf rdf:resource="hasResult"/>
	</rdf:Property>
	<rdf:Property rdf:ID="hasAction">
		<rdfs:comment>An Event can have one or more Actions, which are verbs performed by Agents in the context of the Event.</rdfs:comment>
		<rdfs:domain rdf:resource="Event"/>
		<rdfs:range rdf:resource="Action"/>
	</rdf:Property>
	<rdf:Property rdf:ID="hasAgent">
		<rdfs:comment>Associates a subject with an Action.  The property relation can either be binary or ternary.  In the binary relation the value of the hasAgent property is a literal or an entity of type Agent. In the ternary relation the value is an intermediate node with a hasRole property (that specializes the verb in the Action)  and a value property, with the value being the agent (a literal or an entity of type Agent).</rdfs:comment>
		<rdfs:domain rdf:resource="Action"/>
	</rdf:Property>
	<rdf:Property rdf:ID="hasRole">
		<rdfs:comment>Specializes the participation of an Agent in an Action.  Its domain, although undefined in the schema, will be an intermediate node that is the value of a hasAgent property, and the statement expressed will be ternary relation between Action, role, and Agent.</rdfs:comment>
	</rdf:Property>
	<rdf:Property rdf:ID="atTime">
		<rdfs:comment>Associates a time (of unconstrained type) with an entity that is a sub-category of an Temporality.</rdfs:comment>
		<rdfs:domain rdf:resource="Temporality"/>
	</rdf:Property>
	<rdf:Property rdf:ID="inPlace">
		<rdfs:comment>Associates a location (of unconstrained type) with an entity.  The entity can be an Actuality or Temporality.</rdfs:comment>
		<rdfs:domain rdf:resource="Actuality"/>
		<rdfs:domain rdf:resource="Temporality"/>
	</rdf:Property>
</rdf:RDF>
