Page History

...

• accrualPolicy
  • Domain: Collection
  • Range: Policy
  • Possible DSpace overlap: collection policies?

• alternative
  • Domain: none
  • Range: Literal
  • Possible DSpace overlap: dc.title.alternative

• audience
  • Domain: none
  • Range: AgentClass
  • Possible DSpace overlap: none?

• available
  • Domain: none
  • Range: Literal
  • Possible DSpace overlap: dc.date.available

• bibliographicCitation - INTERESTING ONE
  • Domain: BibliographicResource
  • Range: Literal
  • Possible DSpace overlap: dc.identifier.citation

• conformsTo
  • Domain: none
  • Range: Standard
  • Possible DSpace overlap: none?

• created
  • Domain: none
  • Range: Literal
  • Possible DSpace overlap: dc.date.created

• dateAccepted
  • Domain:none
  • Range: Literal
  • Possible DSpace overlap: none?

• dateCopyrighted
  • Domain:none
  • Range: Literal
  • Possible DSpace overlap: embargo solutions?

• dateSubmitted
  • Domain:none
  • Range: Literal
  • Possible DSpace overlap: dc.date.submitted

• educationLevel
  • Domain:none
  • Range:AgentClass
  • Possible DSpace overlap: none?

• extent
  • Domain:none
  • Range: SizeOrDuration
  • Possible DSpace overlap: dc.format.extent

• hasFormat
  • 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: none?

• hasPart
  • 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.haspart

• hasVersion
  • 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.hasversion

• instructionalMethod
  • Domain: none
  • Range: MethodOfInstruction
  • Possible DSpace overlap: none?

• isFormatOf
  • 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.isformatof

• isPartOf
  • 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.ispartof

• isReferencedBy
  • 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.isreferencedby

• isReplacedBy
  • 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.isreplacedby

• isRequiredBy
  • 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: none?

• issued
  • Domain: none
  • Range: Literal
  • Possible DSpace overlap: dc.date.issued

• 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
  • Domain: none
  • Range: LicenseDocument
  • Possible DSpace overlap: item license

• mediator
  • Domain: none
  • Range: AgentClass
  • Possible DSpace overlap: none?

Possible Approaches

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

...