The Friend of a Friend (FOAF) RDF vocabulary, described using W3C RDF Schema and the Web Ontology Language.
A foaf:LabelProperty is any RDF property with texual values that serve as labels.
An agent (eg. person, group, software or physical artifact).
A project (a collective endeavour of some kind).
A personal mailbox, ie. an Internet mailbox associated with exactly one owner, the first owner of this mailbox. This is a 'static inverse functional property', in that there is (across time and change) at most one individual that ever has any particular value for foaf:mbox.
The sha1sum of the URI of an Internet mailbox associated with exactly one owner, the first owner of the mailbox.
The gender of this Agent (typically but not necessarily 'male' or 'female').
A textual geekcode for this person, see http://www.geekcode.com/geek.html
A checksum for the DNA of some thing. Joke.
A location that something is based near, for some broadly human notion of near.
A short informal nickname characterising an agent (includes login identifiers, IRC and other chat nicknames).
A phone, specified using fully qualified tel: URI scheme (refs: http://www.w3.org/Addressing/schemes.html#tel).
A weblog of some thing (whether person, group, company etc.).
A tipjar document for this agent, describing means for payment and reward.
A .plan comment, in the tradition of finger and '.plan' files.
An image that can be used to represent some thing (ie. those depictions which are particularly representative of something, eg. one's photo on a homepage).
A thing depicted in this representation.
A Myers Briggs (MBTI) personality classification.
A workplace homepage of some person; the homepage of an organization they work for.
A work info homepage of some person; a page about their work for some organization.
A homepage of a school attended by the person.
A person known by this person (indicating some level of reciprocated interaction between the parties).
A page about a topic of interest to this person.
A link to the publications of this person.
A project this person has previously worked on.
An organization funding a project or person.
The primary topic of some page or document.
The underlying or 'focal' entity associated with some SKOS-described concept.
Concept
An idea or notion; a unit of thought.
A document that this thing is the primary topic of.
Indicates an account held by this agent.
Indicates a homepage of the service provide for this online account.
Indicates the name (identifier) associated with this online account.
Indicates the class of individuals that are a member of a Group
The birthday of this Agent, represented in mm-dd string form, eg. '12-31'.
A string expressing what the user is happy for the general public (normally) to know about their current activity.
An activity is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities.
ActivityInfluence provides additional descriptions of an Activity's binary influence upon any other kind of resource. Instances of ActivityInfluence use the prov:activity property to cite the influencing Activity.
It is not recommended that the type ActivityInfluence be asserted without also asserting one of its more specific subclasses.
ActivitiyInfluence is the capacity of an activity to have an effect on the character, development, or behavior of another by means of generation, invalidation, communication, or other.
An agent is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity.
AgentInfluence provides additional descriptions of an Agent's binary influence upon any other kind of resource. Instances of AgentInfluence use the prov:agent property to cite the influencing Agent.
It is not recommended that the type AgentInfluence be asserted without also asserting one of its more specific subclasses.
AgentInfluence is the capacity of an agent to have an effect on the character, development, or behavior of another by means of attribution, association, delegation, or other.
An instance of prov:Association provides additional descriptions about the binary prov:wasAssociatedWith relation from an prov:Activity to some prov:Agent that had some responsiblity for it. For example, :baking prov:wasAssociatedWith :baker; prov:qualifiedAssociation [ a prov:Association; prov:agent :baker; :foo :bar ].
An activity association is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity.
An instance of prov:Attribution provides additional descriptions about the binary prov:wasAttributedTo relation from an provprov:Entity to some prov:Agent that had some responsible for it. For example, :cake prov:wasAttributedTo :baker; prov:qualifiedAttribution [ a prov:Attribution; provprov:Entity :baker; :foo :bar ].
Attribution is the ascribing of an entity to an agent. When an entity e is attributed to agent ag, entity e was generated by some unspecified activity that in turn was associated to agent ag. Thus, this relation is useful when the activity is not known, or irrelevant.
Note that there are kinds of bundles (e.g. handwritten letters, audio recordings, etc.) that are not expressed in PROV-O, but can be still be described by PROV-O.
A bundle is a named set of provenance descriptions, and is itself an Entity, so allowing provenance of provenance to be expressed.
A collection is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be member of the collections.
An instance of prov:Communication provides additional descriptions about the binary prov:wasInformedBy relation from an informed prov:Activity to the prov:Activity that informed it. For example, :you_jumping_off_bridge prov:wasInformedBy :everyone_else_jumping_off_bridge; prov:qualifiedCommunication [ a prov:Communication; prov:activity :everyone_else_jumping_off_bridge; :foo :bar ].
Communication is the exchange of an entity by two activities, one activity using the entity generated by the other.
An instance of prov:Delegation provides additional descriptions about the binary prov:actedOnBehalfOf relation from a performing prov:Agent to some prov:Agent for whom it was performed. For example, :mixing prov:wasAssociatedWith :toddler . :toddler prov:actedOnBehalfOf :mother; prov:qualifiedDelegation [ a prov:Delegation; provprov:Entity :mother; :foo :bar ].
Delegation is the assignment of authority and responsibility to an agent (by itself or by another agent) to carry out a specific activity as a delegate or representative, while the agent it acts on behalf of retains some responsibility for the outcome of the delegated work. For example, a student acted on behalf of his supervisor, who acted on behalf of the department chair, who acted on behalf of the university; all those agents are responsible in some way for the activity that took place but we do not say explicitly who bears responsibility and to what degree.
An instance of prov:Derivation provides additional descriptions about the binary prov:wasDerivedFrom relation from some derived provprov:Entity to another provprov:Entity from which it was derived. For example, :chewed_bubble_gum prov:wasDerivedFrom :unwrapped_bubble_gum; prov:qualifiedDerivation [ a prov:Derivation; provprov:Entity :unwrapped_bubble_gum; :foo :bar ].
The more specific forms of prov:Derivation (i.e., prov:Revision, prov:Quotation, prov:PrimarySource) should be asserted if they apply.
A derivation is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity.
EmptyCollection
An empty collection is a collection without members.
An instance of prov:End provides additional descriptions about the binary prov:wasEndedBy relation from some ended prov:Activity to an provprov:Entity that ended it. For example, :ball_game prov:wasEndedBy :buzzer; prov:qualifiedEnd [ a prov:End; provprov:Entity :buzzer; :foo :bar; prov:atTime '2012-03-09T08:05:08-05:00'^^xsd:dateTime ].
End is when an activity is deemed to have been ended by an entity, known as trigger. The activity no longer exists after its end. Any usage, generation, or invalidation involving an activity precedes the activity's end. An end may refer to a trigger entity that terminated the activity, or to an activity, known as ender that generated the trigger.
An entity is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary.
EntityInfluence provides additional descriptions of an Entity's binary influence upon any other kind of resource. Instances of EntityInfluence use the provprov:Entity property to cite the influencing Entity.
It is not recommended that the type EntityInfluence be asserted without also asserting one of its more specific subclasses.
EntityInfluence is the capacity of an entity to have an effect on the character, development, or behavior of another by means of usage, start, end, derivation, or other.
An instance of prov:Generation provides additional descriptions about the binary prov:wasGeneratedBy relation from a generated provprov:Entity to the prov:Activity that generated it. For example, :cake prov:wasGeneratedBy :baking; prov:qualifiedGeneration [ a prov:Generation; prov:activity :baking; :foo :bar ].
Generation is the completion of production of a new entity by an activity. This entity did not exist before generation and becomes available for usage after this generation.
An instance of prov:Influence provides additional descriptions about the binary prov:wasInfluencedBy relation from some influenced Activity, Entity, or Agent to the influencing Activity, Entity, or Agent. For example, :stomach_ache prov:wasInfluencedBy :spoon; prov:qualifiedInfluence [ a prov:Influence; provprov:Entity :spoon; :foo :bar ] . Because prov:Influence is a broad relation, the more specific relations (Communication, Delegation, End, etc.) should be used when applicable.
Because prov:Influence is a broad relation, its most specific subclasses (e.g. prov:Communication, prov:Delegation, prov:End, prov:Revision, etc.) should be used when applicable.
Influence is the capacity of an entity, activity, or agent to have an effect on the character, development, or behavior of another by means of usage, start, end, generation, invalidation, communication, derivation, attribution, association, or delegation.
An instantaneous event, or event for short, happens in the world and marks a change in the world, in its activities and in its entities. The term 'event' is commonly used in process algebra with a similar meaning. Events represent communications or interactions; they are assumed to be atomic and instantaneous.
The PROV data model is implicitly based on a notion of instantaneous events (or just events), that mark transitions in the world. Events include generation, usage, or invalidation of entities, as well as starting or ending of activities. This notion of event is not first-class in the data model, but it is useful for explaining its other concepts and its semantics.
An instance of prov:Invalidation provides additional descriptions about the binary prov:wasInvalidatedBy relation from an invalidated provprov:Entity to the prov:Activity that invalidated it. For example, :uncracked_egg prov:wasInvalidatedBy :baking; prov:qualifiedInvalidation [ a prov:Invalidation; prov:activity :baking; :foo :bar ].
Invalidation is the start of the destruction, cessation, or expiry of an existing entity by an activity. The entity is no longer available for use (or further invalidation) after invalidation. Any generation or usage of an entity precedes its invalidation.
A location can be an identifiable geographic place (ISO 19112), but it can also be a non-geographic place such as a directory, row, or column. As such, there are numerous ways in which location can be expressed, such as by a coordinate, address, landmark, and so forth.
An organization is a social or legal institution such as a company, society, etc.
Person agents are people.
There exist no prescriptive requirement on the nature of plans, their representation, the actions or steps they consist of, or their intended goals. Since plans may evolve over time, it may become necessary to track their provenance, so plans themselves are entities. Representing the plan explicitly in the provenance can be useful for various tasks: for example, to validate the execution as represented in the provenance record, to manage expectation failures, or to provide explanations.
A plan is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals.
An instance of prov:PrimarySource provides additional descriptions about the binary prov:hadPrimarySource relation from some secondary provprov:Entity to an earlier, primary provprov:Entity. For example, :blog prov:hadPrimarySource :newsArticle; prov:qualifiedPrimarySource [ a prov:PrimarySource; provprov:Entity :newsArticle; :foo :bar ] .
A primary source for a topic refers to something produced by some agent with direct experience and knowledge about the topic, at the time of the topic's study, without benefit from hindsight. Because of the directness of primary sources, they 'speak for themselves' in ways that cannot be captured through the filter of secondary sources. As such, it is important for secondary sources to reference those primary sources from which they were derived, so that their reliability can be investigated. A primary source relation is a particular case of derivation of secondary materials from their primary sources. It is recognized that the determination of primary sources can be up to interpretation, and should be done according to conventions accepted within the application's domain.
An instance of prov:Quotation provides additional descriptions about the binary prov:wasQuotedFrom relation from some taken provprov:Entity from an earlier, larger provprov:Entity. For example, :here_is_looking_at_you_kid prov:wasQuotedFrom :casablanca_script; prov:qualifiedQuotation [ a prov:Quotation; provprov:Entity :casablanca_script; :foo :bar ].
A quotation is the repeat of (some or all of) an entity, such as text or image, by someone who may or may not be its original author. Quotation is a particular case of derivation.
An instance of prov:Revision provides additional descriptions about the binary prov:wasRevisionOf relation from some newer provprov:Entity to an earlier provprov:Entity. For example, :draft_2 prov:wasRevisionOf :draft_1; prov:qualifiedRevision [ a prov:Revision; provprov:Entity :draft_1; :foo :bar ].
A revision is a derivation for which the resulting entity is a revised version of some original. The implication here is that the resulting entity contains substantial content from the original. Revision is a particular case of derivation.
A role is the function of an entity or agent with respect to an activity, in the context of a usage, generation, invalidation, association, start, and end.
A software agent is running software.
An instance of prov:Start provides additional descriptions about the binary prov:wasStartedBy relation from some started prov:Activity to an provprov:Entity that started it. For example, :foot_race prov:wasStartedBy :bang; prov:qualifiedStart [ a prov:Start; provprov:Entity :bang; :foo :bar; prov:atTime '2012-03-09T08:05:08-05:00'^^xsd:dateTime ] .
Start is when an activity is deemed to have been started by an entity, known as trigger. The activity did not exist before its start. Any usage, generation, or invalidation involving an activity follows the activity's start. A start may refer to a trigger entity that set off the activity, or to an activity, known as starter, that generated the trigger.
An instance of prov:Usage provides additional descriptions about the binary prov:used relation from some prov:Activity to an provprov:Entity that it used. For example, :keynote prov:used :podium; prov:qualifiedUsage [ a prov:Usage; provprov:Entity :podium; :foo :bar ].
Usage is the beginning of utilizing an entity by an activity. Before usage, the activity had not begun to utilize this entity and could not have been affected by the entity.
An object property to express the accountability of an agent towards another agent. The subordinate agent acted on behalf of the responsible agent in an actual activity.
This property behaves in spirit like rdf:object; it references the object of a prov:wasInfluencedBy triple.
The prov:activity property references an prov:Activity which influenced a resource. This property applies to an prov:ActivityInfluence, which is given by a subproperty of prov:qualifiedInfluence from the influenced provprov:Entity, prov:Activity or prov:Agent.
Two alternate entities present aspects of the same thing. These aspects may be the same or different, and the alternate entities may or may not overlap in time.
The Location of any resource.
This property has multiple RDFS domains to suit multiple OWL Profiles. See PROV-O OWL Profile.
The naming of prov:atLocation parallels prov:atTime, and is not named prov:hadLocation to avoid conflicting with the convention that prov:had* properties are used on prov:Influence classes.
This property is not functional because the many values could be at a variety of granularies (In this building, in this room, in that chair).
The time at which an InstantaneousEvent occurred, in the form of xsd:dateTime.
Classify prov-o terms into three categories, including 'starting-point', 'qualifed', and 'extended'. This classification is used by the prov-o html document to gently introduce prov-o terms to its users.
Classify prov-o terms into six components according to prov-dm, including 'agents-responsibility', 'alternate', 'annotations', 'collections', 'derivations', and 'entities-activities'. This classification is used so that readers of prov-o specification can find its correspondence with the prov-dm specification.
A reference to the principal section of the PROV-CONSTRAINTS document that describes this concept.
A definition quoted from PROV-DM or PROV-CONSTRAINTS that describes the concept expressed with this OWL term.
A reference to the principal section of the PROV-DM document that describes this concept.
A note by the OWL development team about how this term expresses the PROV-DM concept, or how it should be used in context of semantic web or linked data.
When the prov-o term does not have a definition drawn from prov-dm, and the prov-o editor provides one.
The time at which an activity ended. See also prov:startedAtTime.
It is the intent that the property chain holds: (prov:qualifiedEnd o prov:atTime) rdfs:subPropertyOf prov:endedAtTime.
prov:generated is one of few inverse property defined, to allow Activity-oriented assertions in addition to Entity-oriented assertions.
The time at which an entity was completely created and is available for use.
It is the intent that the property chain holds: (prov:qualifiedGeneration o prov:atTime) rdfs:subPropertyOf prov:generatedAtTime.
The _optional_ Activity of an Influence, which used, generated, invalidated, or was the responsibility of some Entity. This property is _not_ used by ActivityInfluence (use prov:activity instead).
The multiple rdfs:domain assertions are intended. One is simpler and works for OWL-RL, the union is more specific but is not recognized by OWL-RL.
The _optional_ Generation involved in an Entity's Derivation.
The _optional_ Plan adopted by an Agent in Association with some Activity. Plan specifications are out of the scope of this specification.
The _optional_ Role that an Entity assumed in the context of an Activity. For example, :baking prov:used :spoon; prov:qualified [ a prov:Usage; provprov:Entity :spoon; prov:hadRole roles:mixing_implement ].
prov:hadRole references the Role (i.e. the function of an entity with respect to an activity), in the context of an instantaneous usage, generation, association, start, and end.
The _optional_ Usage involved in an Entity's Derivation.
Subproperties of prov:influencer are used to cite the object of an unqualified PROV-O triple whose predicate is a subproperty of prov:wasInfluencedBy (e.g. prov:used, prov:wasGeneratedBy). prov:influencer is used much like rdf:object is used.
This property and its subproperties are used in the same way as the rdf:object property, i.e. to reference the object of an unqualified prov:wasInfluencedBy or prov:influenced triple.
This property is used as part of the qualified influence pattern. Subclasses of prov:Influence use these subproperties to reference the resource (Entity, Agent, or Activity) whose influence is being qualified.
prov:invalidated is one of few inverse property defined, to allow Activity-oriented assertions in addition to Entity-oriented assertions.
The time at which an entity was invalidated (i.e., no longer usable).
It is the intent that the property chain holds: (prov:qualifiedInvalidation o prov:atTime) rdfs:subPropertyOf prov:invalidatedAtTime.
PROV-O does not define all property inverses. The directionalities defined in PROV-O should be given preference over those not defined. However, if users wish to name the inverse of a PROV-O property, the local name given by prov:inverse should be used.
The position that this OWL term should be listed within documentation. The scope of the documentation (e.g., among all terms, among terms within a prov:category, among properties applying to a particular class, etc.) is unspecified.
If this Activity prov:wasAssociatedWith Agent :ag, then it can qualify the Association using prov:qualifiedAssociation [ a prov:Association; prov:agent :ag; :foo :bar ].
If this Entity prov:wasAttributedTo Agent :ag, then it can qualify how it was influenced using prov:qualifiedAttribution [ a prov:Attribution; prov:agent :ag; :foo :bar ].
If this Activity prov:wasInformedBy Activity :a, then it can qualify how it was influenced using prov:qualifiedCommunication [ a prov:Communication; prov:activity :a; :foo :bar ].
If this Agent prov:actedOnBehalfOf Agent :ag, then it can qualify how with prov:qualifiedResponsibility [ a prov:Responsibility; prov:agent :ag; :foo :bar ].
If this Entity prov:wasDerivedFrom Entity :e, then it can qualify how it was derived using prov:qualifiedDerivation [ a prov:Derivation; provprov:Entity :e; :foo :bar ].
If this Activity prov:wasEndedBy Entity :e1, then it can qualify how it was ended using prov:qualifiedEnd [ a prov:End; provprov:Entity :e1; :foo :bar ].
This annotation property links a subproperty of prov:wasInfluencedBy with the subclass of prov:Influence and the qualifying property that are used to qualify it. Example annotation: prov:wasGeneratedBy prov:qualifiedForm prov:qualifiedGeneration, prov:Generation . Then this unqualified assertion: prov:Entity1 prov:wasGeneratedBy :activity1 . can be qualified by adding: prov:Entity1 prov:qualifiedGeneration prov:Entity1Gen . prov:Entity1Gen a prov:Generation, prov:Influence; prov:activity :activity1; :customValue 1337 . Note how the value of the unqualified influence (prov:wasGeneratedBy :activity1) is mirrored as the value of the prov:activity (or provprov:Entity, or prov:agent) property on the influence class.
If this Activity prov:generated Entity :e, then it can qualify how it performed the Generation using prov:qualifiedGeneration [ a prov:Generation; provprov:Entity :e; :foo :bar ].
Because prov:qualifiedInfluence is a broad relation, the more specific relations (qualifiedCommunication, qualifiedDelegation, qualifiedEnd, etc.) should be used when applicable.
If this Entity prov:wasInvalidatedBy Activity :a, then it can qualify how it was invalidated using prov:qualifiedInvalidation [ a prov:Invalidation; prov:activity :a; :foo :bar ].
If this Entity prov:hadPrimarySource Entity :e, then it can qualify how using prov:qualifiedPrimarySource [ a prov:PrimarySource; provprov:Entity :e; :foo :bar ].
If this Entity prov:wasQuotedFrom Entity :e, then it can qualify how using prov:qualifiedQuotation [ a prov:Quotation; provprov:Entity :e; :foo :bar ].
If this Entity prov:wasRevisionOf Entity :e, then it can qualify how it was revised using prov:qualifiedRevision [ a prov:Revision; provprov:Entity :e; :foo :bar ].
If this Activity prov:wasStartedBy Entity :e1, then it can qualify how it was started using prov:qualifiedStart [ a prov:Start; provprov:Entity :e1; :foo :bar ].
If this Activity prov:used Entity :e, then it can qualify how it used it using prov:qualifiedUsage [ a prov:Usage; provprov:Entity :e; :foo :bar ].
An entity that is a specialization of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the entity being specialized contains that of any specialization. Examples of aspects include a time period, an abstraction, and a context associated with the entity.
The time at which an activity started. See also prov:endedAtTime.
It is the intent that the property chain holds: (prov:qualifiedStart o prov:atTime) rdfs:subPropertyOf prov:startedAtTime.
Classes and properties used to qualify relationships are annotated with prov:unqualifiedForm to indicate the property used to assert an unqualified provenance relation.
A provprov:Entity that was used by this prov:Activity. For example, :baking prov:used :spoon, :egg, :oven .
Provides a value that is a direct representation of an entity.
The editor's definition comes from http://www.w3.org/TR/rdf-primer/#rdfvalue
This property serves the same purpose as rdf:value, but has been reintroduced to avoid some of the definitional ambiguity in the RDF specification (specifically, 'may be used in describing structured values').
An prov:Agent that had some (unspecified) responsibility for the occurrence of this prov:Activity.
Attribution is the ascribing of an entity to an agent.
The more specific subproperties of prov:wasDerivedFrom (i.e., prov:wasQuotedFrom, prov:wasRevisionOf, prov:hadPrimarySource) should be used when applicable.
End is when an activity is deemed to have ended. An end may refer to an entity, known as trigger, that terminated the activity.
Because prov:wasInfluencedBy is a broad relation, its more specific subproperties (e.g. prov:wasInformedBy, prov:actedOnBehalfOf, prov:wasEndedBy, etc.) should be used when applicable.
The sub-properties of prov:wasInfluencedBy can be elaborated in more detail using the Qualification Pattern. For example, the binary relation :baking prov:used :spoon can be qualified by asserting :baking prov:qualifiedUsage [ a prov:Usage; provprov:Entity :spoon; prov:atLocation :kitchen ] . Subproperties of prov:wasInfluencedBy may also be asserted directly without being qualified. prov:wasInfluencedBy should not be used without also using one of its subproperties.
An activity a2 is dependent on or informed by another activity a1, by way of some unspecified entity that is generated by a1 and used by a2.
An entity is derived from an original entity by copying, or 'quoting', some or all of it.
A revision is a derivation that revises an entity into a revised version.
Start is when an activity is deemed to have started. A start may refer to an entity, known as trigger, that initiated the activity.
This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page). If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome.
W3C PROVenance Interchange Ontology (PROV-O)
Recommendation version 2013-04-30
Participants in W3C's Semantic Web Deployment Working Group.
An RDF vocabulary for describing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', other types of controlled vocabulary, and also concept schemes embedded in glossaries and terminologies.
SKOS Vocabulary
Concept Scheme
A set of concepts, optionally including statements about semantic relationships between those concepts.
Thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', and other types of controlled vocabulary are all examples of concept schemes. Concept schemes are also embedded in glossaries and terminologies.
A concept scheme may be defined to include concepts from different sources.
Collection
A meaningful collection of concepts.
Labelled collections can be used where you would like a set of concepts to be displayed under a 'node label' in the hierarchy.
Ordered Collection
An ordered collection of concepts, where both the grouping and the ordering are meaningful.
Ordered collections can be used where you would like a set of concepts to be displayed in a specific order, and optionally under a 'node label'.
is in scheme
Relates a resource (for example a concept) to a concept scheme in which it is included.
A concept may be a member of more than one concept scheme.
has top concept
Relates, by convention, a concept scheme to a concept which is topmost in the broader/narrower concept hierarchies for that scheme, providing an entry point to these hierarchies.
is top concept in scheme
Relates a concept to the concept scheme that it is a top level concept of.
A resource has no more than one value of skos:prefLabel per language tag, and no more than one value of skos:prefLabel without language tag.
The range of skos:prefLabel is the class of RDF plain literals.
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties.
preferred label
The preferred lexical label for a resource, in a given language.
The range of skos:altLabel is the class of RDF plain literals.
alternative label
An alternative lexical label for a resource.
Acronyms, abbreviations, spelling variants, and irregular plural/singular forms may be included among the alternative labels for a concept. Mis-spelled terms are normally included as hidden labels (see skos:hiddenLabel).
The range of skos:hiddenLabel is the class of RDF plain literals.
hidden label
A lexical label for a resource that should be hidden when generating visual displays of the resource, but should still be accessible to free text search operations.
notation
A notation, also known as classification code, is a string of characters such as "T58.5" or "303.4833" used to uniquely identify a concept within the scope of a given concept scheme.
By convention, skos:notation is used with a typed literal in the object position of the triple.
note
A general note, for any purpose.
This property may be used directly, or as a super-property for more specific note types.
change note
A note about a modification to a concept.
definition
A statement or formal explanation of the meaning of a concept.
editorial note
A note for an editor, translator or maintainer of the vocabulary.
example
An example of the use of a concept.
history note
A note about the past state/use/meaning of a concept.
scope note
A note that helps to clarify the meaning and/or the use of a concept.
is in semantic relation with
Links a concept to a concept related by meaning.
This property should not be used directly, but as a super-property for all properties denoting a relationship of meaning between concepts.
Broader concepts are typically rendered as parents in a concept hierarchy (tree).
has broader
Relates a concept to a concept that is more general in meaning.
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.
Narrower concepts are typically rendered as children in a concept hierarchy (tree).
has narrower
Relates a concept to a concept that is more specific in meaning.
skos:related is disjoint with skos:broaderTransitive
has related
Relates a concept to a concept with which there is an associative semantic relationship.
has broader transitive
skos:broaderTransitive is a transitive superproperty of skos:broader.
By convention, skos:broaderTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.
has narrower transitive
skos:narrowerTransitive is a transitive superproperty of skos:narrower.
By convention, skos:narrowerTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.
has member
Relates a collection to one of its members.
For any resource, every item in the list given as the value of the skos:memberList property is also a value of the skos:member property.
has member list
Relates an ordered collection to the RDF list containing its members.
These concept mapping relations mirror semantic relations, and the data model defined below is similar (with the exception of skos:exactMatch) to the data model defined for semantic relations. A distinct vocabulary is provided for concept mapping relations, to provide a convenient way to differentiate links within a concept scheme from links between concept schemes. However, this pattern of usage is not a formal requirement of the SKOS data model, and relies on informal definitions of best practice.
is in mapping relation with
Relates two concepts coming, by convention, from different schemes, and that have comparable meanings
has broader match
skos:broadMatch is used to state a hierarchical mapping link between two conceptual resources in different concept schemes.
has narrower match
skos:narrowMatch is used to state a hierarchical mapping link between two conceptual resources in different concept schemes.
has related match
skos:relatedMatch is used to state an associative mapping link between two conceptual resources in different concept schemes.
skos:exactMatch is disjoint with each of the properties skos:broadMatch and skos:relatedMatch.
has exact match
skos:exactMatch is used to link two concepts, indicating a high degree of confidence that the concepts can be used interchangeably across a wide range of information retrieval applications. skos:exactMatch is a transitive property, and is a sub-property of skos:closeMatch.
has close match
skos:closeMatch is used to link two concepts that are sufficiently similar that they can be used interchangeably in some information retrieval applications. In order to avoid the possibility of "compound errors" when combining mappings across more than two concept schemes, skos:closeMatch is not declared to be a transitive property.
Process of inputting something into the case base.
input
The process of reusing a case for a problem.
reuse case
Fall 1
case 1
Defines the value a certain case attribute has been set to.
case
A case is connected to solving a specific problem.
has problem
A case has attributes with values assigned.
attribute value tuple
The process of retrieving cases from the case base.
retrieve case
If an explosion happens, call the firefighters.
Fall 2
case 2
has Input
The process of retaining a case in the case base.
retain case
A case is defined by attributes and values.
has attribute value tuple
Cases can be related.
related to
A case describes a successfully used solution for a problem.
The case-based reasoning concept encompasses all sub-concepts necessary to implement the case-based reasoning cycle and paradigm.
case-based reasoning
Defines the problem the case solved.
case problem
States represent the components of the CBR cycle.
output
The problem connected to the case is corrected by the solution.
has solution
The cases problem and solution may be defined by attributes.
has attribute
A case has a description of an arbitrary type.
has description
A case may have attributes that are used to define the case description, problem, and solution.
case attributes
The process of revising a case.
revise case
The case base communicates to the environment.
environment
Fall 3
case 3
If a fire happens, put it out with water.
The attributes defining problem and solution are assigned with values.
has inferior measure
Responsibility
A case can be part of a case base.
part of
Defines the solution the case used to solve the problem.
case solution
Defines the case, e.g., by using text, variables, numbers.
case description
The case base aggregates cases and provides interfaces to access them.
case base
hadPrimarySource property is a particular case of wasDerivedFrom (see http://www.w3.org/TR/prov-dm/#term-original-source) that aims to give credit to the source that originated some information.
Attribution is a particular case of trace (see http://www.w3.org/TR/prov-dm/#concept-trace), in the sense that it links an entity to the agent that ascribed it.
IF wasAttributedTo(e2,ag1,aAttr) holds, THEN wasInfluencedBy(e2,ag1) also holds.
Derivation is a particular case of trace (see http://www.w3.org/TR/prov-dm/#term-trace), since it links an entity to another entity that contributed to its existence.
influencer: an identifier (o1) for an ancestor entity, activity, or agent that the former depends on;
influencee: an identifier (o2) for an entity, activity, or agent;
Quotation is a particular case of derivation (see http://www.w3.org/TR/prov-dm/#term-quotation) in which an entity is derived from an original entity by copying, or "quoting", some or all of it.
Revision is a derivation (see http://www.w3.org/TR/prov-dm/#term-Revision). Moreover, according to http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#term-Revision 23 April 2012 'wasRevisionOf is a strict sub-relation of wasDerivedFrom since two entities e2 and e1 may satisfy wasDerivedFrom(e2,e1) without being a variant of each other.'