Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

The existing 15 elements were extended with range and domain and new elements were added. To ensure "backwards compatibility" with existing implementations, these new changes were located in a new namespace, dcterms:
So dc:creator can't be confused with dcterms:creator, a property that can now have a range and domain.

http://dublincore.org/documents/dcmi-terms/

Goals for DSpace

Exposing DSpace metadata in the dcterms namespace

...

  • isVersionOf
    • Domain: none
    • Range: none (YET)
    • Note: This term is intended to be used with NON-LITERAL values. As of December 2007, the DCMI Usage board is seeking a way to express this intention with a formal range declaration.
    • Possible DSpace overlap: dc.relation.isversionof
  • license Tricky one TRICKY ONE
    • Domain: none
    • Range: LicenseDocument
    • Possible DSpace overlap: item license
  • mediator
    • Domain: none
    • Range: AgentClass
    • Possible DSpace overlap: none?
  • medium
    • Domain: PhysicalResource
    • Range: PhysicalMedium
    • Possible DSpace overlap: dc.format.medium
  • modified
    • Domain: none
    • Range: Literal
    • Possible DSpace overlap: dc.date.updated (wasn't there a dc.date.modified????)
  • provenance
    • Domain: none
    • Range: ProvenanceStatement
    • Possible DSpace overlap: dc.description.provenance
  • references
    • Domain: none
    • Range: none (YET)
    • Note: This term is intended to be used with NON-LITERAL values. As of December 2007, the DCMI Usage board is seeking a way to express this intention with a formal range declaration.
    • Possible DSpace overlap: dc.citation ????????????
  • replaces
    • Domain: none
    • Range: none (YET)
    • Note: This term is intended to be used with NON-LITERAL values. As of December 2007, the DCMI Usage board is seeking a way to express this intention with a formal range declaration.
    • Possible DSpace overlap: dc.relation.replaces
  • requires
    • Domain: none
    • Range: none (YET)
    • Note: This term is intended to be used with NON-LITERAL values. As of December 2007, the DCMI Usage board is seeking a way to express this intention with a formal range declaration.
    • Possible DSpace overlap: dc.relation.requires
  • rightsHolder
    • Domain: none
    • Range: Agent
    • Possible DSpace overlap: dc.rights.holder
  • spatial
    • Domain: none
    • Range: Location
    • Possible DSpace overlap: dc.coverage.spatial

Possible Approaches

Adding a new schema dcterms that lives next to the standard dc schema

...