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"
(→Classes) |
|||
Line 19: | Line 19: | ||
#* 0..1 lastVerifyAttempt | #* 0..1 lastVerifyAttempt | ||
# ComplexAttribute (subclass of Attribute) | # ComplexAttribute (subclass of Attribute) | ||
− | # | + | # ContextId - URI of a Context |
# ContextObject | # ContextObject | ||
#* 0..N hasContextRelationships | #* 0..N hasContextRelationships | ||
# ContextRelationship | # ContextRelationship | ||
− | #* 0..N | + | #* 0..N contextId |
# SimpleAttribute (subclass of Attribute) | # SimpleAttribute (subclass of Attribute) | ||
#* 1..N simpleValue | #* 1..N simpleValue | ||
Line 31: | Line 31: | ||
#* 0..N attribute | #* 0..N attribute | ||
# SubjectRelationship (subclass of ComplexAttribute) (see [[Subject Relationship]]) | # SubjectRelationship (subclass of ComplexAttribute) (see [[Subject Relationship]]) | ||
− | #* 1..1 | + | #* 1..1 contextId |
− | #* 1..1 | + | #* 1..1 subjectId |
# Correlation (subclass of SubjectRelationship). 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. | # Correlation (subclass of SubjectRelationship). 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 | ||
Line 39: | Line 39: | ||
=====Subclasses of SimpleAttribute===== | =====Subclasses of SimpleAttribute===== | ||
− | # | + | The following mirror the XML Schema types recommended for use with OWL |
− | # | + | # AnyURI |
− | # | + | # Base64Binary |
− | # | + | # Boolean |
− | ...etc | + | # Byte |
+ | # Date | ||
+ | ...etc | ||
====DataType (literal valued) Properties==== | ====DataType (literal valued) Properties==== |
Revision as of 14:24, 3 February 2007
Published URL
http://www.eclipse.org/higgins/ontologies/2006/higgins.owl
Description
The data model of a Context is defined in higgins.owl and summarized below.
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.
Classes
- Attribute (see Identity Attribute)
- 0..N source
- 0..N timeSpan
- 0..1 lastModified
- 0..1 syncConflict
- 0..1 lastVerifiedFromSource
- 0..1 lastVerifyAttempt
- ComplexAttribute (subclass of Attribute)
- ContextId - URI of a Context
- ContextObject
- 0..N hasContextRelationships
- ContextRelationship
- 0..N contextId
- SimpleAttribute (subclass of Attribute)
- 1..N simpleValue
- Digital Subject
- 1..1 uniqueIdentifier
- 0..N timeSpan
- 0..N attribute
- SubjectRelationship (subclass of ComplexAttribute) (see Subject Relationship)
- 1..1 contextId
- 1..1 subjectId
- Correlation (subclass of SubjectRelationship). 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
Subclasses of SimpleAttribute
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(SubjectRelationship), 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
- base64BinarySimpleValue - domain(Base64SimpleAttribute), range(xsd:base64Binary)
- integerSimpleValue - domain(IntegerSimpleAttribute), range(xsd:integer)
- normalizedStringSimpleValue - domain(NormalizedStringSimpleAttribute), range(xsd:normalizedString)
- stringSimpleValue - domain(StringSimpleAttribute), range(xsd:string)
...etc for all of the rest of the XML Schema datatypes
Object (object valued) Properties
- attribute - domain(DigitalSubject), range(Attribute)
- complexMetadata - domain(DigitalSubject, Attribute)
- complexValue - domain(ComplexAttribute)
- contextID - domain(ContextRelationship, SubjectRelationship), range(ContextID)
- contextRelationship - domain(ContextObject), range(ContextRelationship)
- source - domain(Attribute), range(SubjectRelationship). The value is a SubjectRelationship 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
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>