Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Higgins.owl 1.0"
Line 1: | Line 1: | ||
− | + | This page summarizes the higgins.owl ontology here http://www.eclipse.org/higgins/ontologies/2006/higgins.owl | |
− | + | ||
− | http://www.eclipse.org/higgins/ontologies/2006/higgins.owl | + | |
− | + | Every [[Context]] can defines its own ontology. This ontology defines the classes and attributes that that in turn describe data instances within a [[Context]] dataset. This Context-defined ontology must be based on higgins.owl. | |
− | + | ||
− | + | ==Classes== | |
+ | This section is a summary of the main classes in higgins.owl. Each numbered item lists a class (e.g. "Attribute"). The sub-items show properties defined for this class (e.g. "source") prefixed by the cardinality of this property on this class (e.g. "O..N"). | ||
− | + | Note: subclasses of SimpleValue are listed separately in the next section to reduce clutter. | |
+ | # Attribute. Instances of this class are used as the domain of higgins:metadata properties that, taken together, are considered to be the metadata about a higgins:attribute sub-property. | ||
− | + | Classes in alphabetic order: | |
− | + | ||
− | + | ||
# ComplexValue (subclass of Value) | # ComplexValue (subclass of Value) | ||
# ContextId - URI of a Context | # ContextId - URI of a Context | ||
Line 18: | Line 15: | ||
#* 0..N hasContextRelations | #* 0..N hasContextRelations | ||
#* UNDER DISCUSSION: the set of N optional metadata properties | #* UNDER DISCUSSION: the set of N optional metadata properties | ||
− | # | + | # ContextRelation |
#* 0..N contextId | #* 0..N contextId | ||
# SimpleValue (subclass of Value) | # SimpleValue (subclass of Value) | ||
Line 26: | Line 23: | ||
#* 0..N timeSpan | #* 0..N timeSpan | ||
#* 0..N attribute | #* 0..N attribute | ||
− | # | + | # SubjectRelation (subclass of ComplexValue) (see [[Subject Relation]]) |
#* 1..1 contextId | #* 1..1 contextId | ||
#* 1..1 subjectId | #* 1..1 subjectId | ||
− | # Correlation (subclass of | + | # Correlation (subclass of SubjectRelation). If DigitalSubject A has a Correlation relation to DigitalSubject B then this implies that that A and B represent different facets (personas, roles, etc.) of the same underlying Entity. This relation only navigable in one direction: in this example from A to B. |
# TimeSpan | # TimeSpan | ||
#* 0..1 validFrom --if not present, assume validFrom is the beginning of time | #* 0..1 validFrom --if not present, assume validFrom is the beginning of time | ||
Line 43: | Line 40: | ||
#* 0..1 lastVerifyAttempt | #* 0..1 lastVerifyAttempt | ||
− | + | ===Subclasses of SimpleValue=== | |
The following mirror the XML Schema types recommended for use with OWL | The following mirror the XML Schema types recommended for use with OWL | ||
# AnyURI | # AnyURI | ||
Line 52: | Line 49: | ||
...etc | ...etc | ||
− | + | ==DataType (literal valued) Properties== | |
# lastModified - domain(AttributeMetadata), range(xsd:dateTime) | # lastModified - domain(AttributeMetadata), range(xsd:dateTime) | ||
# lastVerifiedFromSource - domain(Attribute), range(xsd:dateTime) | # lastVerifiedFromSource - domain(Attribute), range(xsd:dateTime) | ||
Line 63: | Line 60: | ||
# validTo - domain(TimeSpan), range(xsd:date) | # validTo - domain(TimeSpan), range(xsd:date) | ||
− | + | ==Sub-Properties of simpleValue== | |
# anyURI - domain(AnyURI), range(xsd:anyURI) | # anyURI - domain(AnyURI), range(xsd:anyURI) | ||
# boolean - domain(Boolean), range(xsd:boolean) | # boolean - domain(Boolean), range(xsd:boolean) | ||
Line 69: | Line 66: | ||
...etc for all of the rest of the XML Schema datatypes | ...etc for all of the rest of the XML Schema datatypes | ||
− | + | ==Object (object valued) Properties== | |
# attribute - domain(DigitalSubject, ContextObject, ComplexValue), range(Value, Attribute) | # attribute - domain(DigitalSubject, ContextObject, ComplexValue), range(Value, Attribute) | ||
# complexMetadata - domain(DigitalSubject, Attribute) | # complexMetadata - domain(DigitalSubject, Attribute) | ||
Line 79: | Line 76: | ||
# uniqueIdentifier - domain(DigitalSubject), range(higgins:StringSimpleAttribute). Uniquely identifies a DigitalSubject within a context | # uniqueIdentifier - domain(DigitalSubject), range(higgins:StringSimpleAttribute). Uniquely identifies a DigitalSubject within a context | ||
− | + | ==Annotation Properties== | |
The following have been copied verbatim from http://protege.stanford.edu/plugins/owl/owl-library/2005/08/07/xsp.owl. These allow us to express the semantics of XML Schema within a Higgins-based ontology RDF file. | The following have been copied verbatim from http://protege.stanford.edu/plugins/owl/owl-library/2005/08/07/xsp.owl. These allow us to express the semantics of XML Schema within a Higgins-based ontology RDF file. | ||
# base | # base | ||
Line 93: | Line 90: | ||
# totalDigits | # totalDigits | ||
− | ===CVS Access | + | == Misc Notes == |
+ | The value of the uniqueIdentifier attribute is immutable. All [[Digital Subject]]s have exactly one uniqueIdentifier attribute whose value is set when the [[Digital Subject]] is instantiated. | ||
+ | |||
+ | ''Note: The properties of the Context container itself are attached to special object called ContextObject within the instance data and also described in the ontology.'' | ||
+ | |||
+ | ==CVS Access== | ||
The following Eclipse Team Project Set (.psf) will give you access to the higgins.owl source file: | The following Eclipse Team Project Set (.psf) will give you access to the higgins.owl source file: | ||
<?xml version="1.0" encoding="UTF-8"?> | <?xml version="1.0" encoding="UTF-8"?> |
Revision as of 15:06, 14 September 2007
This page summarizes the higgins.owl ontology here http://www.eclipse.org/higgins/ontologies/2006/higgins.owl
Every Context can defines its own ontology. This ontology defines the classes and attributes that that in turn describe data instances within a Context dataset. This Context-defined ontology must be based on higgins.owl.
Contents
Classes
This section is a summary of the main classes in higgins.owl. Each numbered item lists a class (e.g. "Attribute"). The sub-items show properties defined for this class (e.g. "source") prefixed by the cardinality of this property on this class (e.g. "O..N").
Note: subclasses of SimpleValue are listed separately in the next section to reduce clutter.
- Attribute. Instances of this class are used as the domain of higgins:metadata properties that, taken together, are considered to be the metadata about a higgins:attribute sub-property.
Classes in alphabetic order:
- ComplexValue (subclass of Value)
- ContextId - URI of a Context
- ContextObject
- 0..N hasContextRelations
- UNDER DISCUSSION: the set of N optional metadata properties
- ContextRelation
- 0..N contextId
- SimpleValue (subclass of Value)
- 1..N simpleValue
- Digital Subject
- 1..1 uniqueIdentifier
- 0..N timeSpan
- 0..N attribute
- SubjectRelation (subclass of ComplexValue) (see Subject Relation)
- 1..1 contextId
- 1..1 subjectId
- Correlation (subclass of SubjectRelation). If DigitalSubject A has a Correlation relation to DigitalSubject B then this implies that that A and B represent different facets (personas, roles, etc.) of the same underlying Entity. This relation only navigable in one direction: in this example from A to B.
- TimeSpan
- 0..1 validFrom --if not present, assume validFrom is the beginning of time
- 0..1 validTo --if not present, assume validTo is the end of time
- Value
- 0..N source
- PROPOSED: 0..N creator
- PROPOSED: 0..N creationTime
- 0..N timeSpan
- 0..1 lastModified
- 0..1 syncConflict
- 0..1 lastVerifiedFromSource
- 0..1 lastVerifyAttempt
Subclasses of SimpleValue
The following mirror the XML Schema types recommended for use with OWL
- AnyURI
- Base64Binary
- Boolean
- Byte
- Date
...etc
DataType (literal valued) Properties
- lastModified - domain(AttributeMetadata), range(xsd:dateTime)
- lastVerifiedFromSource - domain(Attribute), range(xsd:dateTime)
- lastVerifyAttempt - domain(Attribute), range(xsd:dateTime)
- simpleMetadata - domain(Attribute, DigitalSubject)
- simpleValue - domain(SimpleAttribute)
- subjectCUID - domain(SubjectRelation), range(xsd:normalizedString)
- syncConflict - domain(AttributeMetadata), range(xsd:boolean)
- validFrom - domain(TimeSpan), range(xsd:date)
- validTo - domain(TimeSpan), range(xsd:date)
Sub-Properties of simpleValue
- anyURI - domain(AnyURI), range(xsd:anyURI)
- boolean - domain(Boolean), range(xsd:boolean)
- base64Binary - domain(Base64), range(xsd:base64Binary)
...etc for all of the rest of the XML Schema datatypes
Object (object valued) Properties
- attribute - domain(DigitalSubject, ContextObject, ComplexValue), range(Value, Attribute)
- complexMetadata - domain(DigitalSubject, Attribute)
- complexValue - domain(ComplexAttribute)
- contextID - domain(ContextRelation, SubjectRelation), range(ContextID)
- contextRelation - domain(ContextObject), range(ContextRelation)
- source - domain(Attribute), range(SubjectRelation). The value is a SubjectRelation that indicates the authoritative source of the value of this Attribute
- timeSpan - domain(DigitalSubject, Attribute), range(TimeSpan)
- uniqueIdentifier - domain(DigitalSubject), range(higgins:StringSimpleAttribute). Uniquely identifies a DigitalSubject within a context
Annotation Properties
The following have been copied verbatim from http://protege.stanford.edu/plugins/owl/owl-library/2005/08/07/xsp.owl. These allow us to express the semantics of XML Schema within a Higgins-based ontology RDF file.
- base
- fractionDigits
- length
- maxExclusive
- maxInclusive
- maxLength
- minExclusive
- minInclusive
- minLength
- pattern
- totalDigits
Misc Notes
The value of the uniqueIdentifier attribute is immutable. All Digital Subjects have exactly one uniqueIdentifier attribute whose value is set when the Digital Subject is instantiated.
Note: The properties of the Context container itself are attached to special object called ContextObject within the instance data and also described in the ontology.
CVS Access
The following Eclipse Team Project Set (.psf) will give you access to the higgins.owl source file:
<?xml version="1.0" encoding="UTF-8"?> <psf version="2.0"> <provider id="org.eclipse.team.cvs.core.cvsnature"> <project reference="1.0, :extssh:dev.eclipse.org:/cvsroot/technology, org.eclipse.higgins/ontology,org.eclipse.higgins.ontology"/> </provider> </psf>