Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Higgins.owl 1.0"

Line 1: Line 1:
The current Higgins ontology temporarily located here:[[Higgins.owl]] (previous: [http://spwiki.editme.com/files/HigginsOntology/higgins0.5.1.owl here (v0.5.1)]) defines a base set of classes and properties. A still earlier version (v0.4.4) is still located at the official URL here:  http://www.eclipse.org/higgins/ontologies/2006/higgins.owl but it will be replaced after a review of 0.5.1 has concluded.
+
This page describes higgins.owl. Versions:
 +
* [http://spwiki.editme.com/Higgins0-5-5 Higgins.owl version 0.5.5] --the latest draft under review
 +
* http://www.eclipse.org/higgins/ontologies/2006/higgins.owl --the currently published version
  
 
''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.''  
 
''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.''  
 
Changes from 0.4.4 to 0.5.0:
 
# ContextXRI property has been renamed ContextURI (the URI may be an XRI)
 
# All "metadata" properties have been moved from AttributeStatements to a newly created class AttributeMetadata. This new class acts separates out metadata about Attributes (e.g. source) from the normal "values" of Attributes.
 
# Two new kinds of metadata have been added: lastModified and syncConflict
 
# XML/RDF in general has been cleaned up (more use of &xsd; &owl; etc.)
 
# Ontology header has been cleaned up. It uses the owl:Ontology syntax. It has a version number (0.5.0). It also now also has a comment and a label.
 
 
  
 
==Classes==
 
==Classes==

Revision as of 01:09, 11 September 2006

This page describes higgins.owl. Versions:

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

  1. AttributeMetadata
    • 0..1 hasSource
    • 0..N hasTimeSpan
    • 0..1 lastModified
    • 0..1 syncConflict
  2. AttributeValue
    • 0..1 hasMetadata
    • 0..1 objectValue
    • 0..1 datatypeValue
  3. ContextObject
    • 0..N hasContextRelationships
  4. ContextRelationship
    • 0..N contextURI
  5. DatatypeAttributeValue
    • 1..N datypeValue
  6. DigitalSubject (see Digital Subject)
    • 1..1 uniqueIdentifier
    • 0..N hasTimeSpan
  7. ObjectAttributeValue
    • 0..N objectValue
  8. SubjectRelationship
    • 1..1 contextURI
    • 1..1 subjectCUID
  9. TimeSpan
    • 1..1 validFrom
    • 1..1 validTo

Subclasses of DatatypeAttributeValue

  1. StringDatatypeAttributeValue
  2. ...we need to create all the rest here (DateAttributeValue, NonNegativeIntegerAttributeValue, etc. for each of the XML Schema literal types used by OWL)

DataType (literal valued) Properties

  1. contextURI - domain(ContextRelationship, SubjectRelationship), range("anyURI")
  2. datatypeValue - domain(AttributeValue)
  3. identifier - domain(AttributeStatement), range(xsd:normalizedString)
  4. lastModified - domain(AttributeMetadata), range(xsd:dateTime)
  5. subjectCUID - domain(SubjectRelationship), range(xsd:normalizedString)
  6. syncConflict - domain(AttributeMetadata), range(xsd:boolean)
  7. uniqueIdentifier - domain(DigitalSubject), range(xsd:normalizedString). Uniquely identifies a DigitalSubject within a context
  8. validFrom - domain(TimeSpan), range(xsd:date)
  9. validTo - domain(TimeSpan), range(xsd:date)

Sub-Properties of datatypeValue

  1. stringDatatypeValue - range(xsd:string)

Object (object valued) Properties

  1. hasContextRelationship - domain(ContextObject), range(ContextRelationship)
  2. hasMetadata - domain(AttributeStatement), range(AttributeMetadata)
  3. hasSource - domain(AttributeMetadata), range(SubjectRelationship). The value is a DigitalSubjectRelationship that indicates the authoritative source of the AttributeStatement having this property
  4. hasTimeSpan - domain(DigitalSubject, AttributeMetadata), range(TimeSpan)
  5. objectValue - domain(AttributeValue)

Open Issues

  1. We've agreed to add a "source" property to the Digital Subject's CUID. But does this really make sense at the DS instance level?

Back to the top