Date: Thu, 28 Mar 2024 13:44:37 -0400 (EDT)
Message-ID: <1371009366.28496.1711647877619@lyrasis1-roc-mp1>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_28495_805786837.1711647877619"
------=_Part_28495_805786837.1711647877619
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Adapting DSpace to Current Dublin Core Standards
Current Dublin Core Status=
1998-2008
There were 15 dublin core elements in the dc: namespace=
. All of these elements were optional and repeatable. DSpace, OAI-PMH, ... =
were based on these elements.
contributor, coverage, creator, date, description, format, identi=
fier, language, publisher, relation, rights, <=
a class=3D"external-link" href=3D"http://dublincore.org/documents/dcmi-term=
s/#elements-source" rel=3D"nofollow">source, subject, title, =
type
Post 2008
The existing 15 elements were extended with range and domain and new ele=
ments were added. To ensure "backwards compatibility" with existing impleme=
ntations, these new changes were located in a new namespace, dcterm=
s:
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
If other new standards or applications will require the use of the dcter=
ms: namespace instead of the dc: namespace, DSpace won't be able to comply.=
Implementing/Verify range for prop=
erties that require this - Needed for both New and Existing properties
Range defines the vocabulary or syntax which must be followed by a prope=
rty. For example, the coverage property has following range:
http://purl.org/dc/terms/LocationPeriodO=
rJurisdiction
Examples: Format has the range MediaTypeorExtent and it's recommended to=
use the MIME types there.
Implementing/Verify domain for properties th=
at require this - Only needed for New Properties
If a dcterm property specifies a domain, it means that the property can =
only be applied to a specific type of item it describes.
Example: The new term BibliographicCitation has the domain Bibliographic=
resource. This means that by specifying the property BibliographicCitation=
, it automatically implies that the item you're applying it to is a bibliog=
raphic resource.
Concr=
ete changes for specific existing properties
- Contributor=20
- Domain: none
- Range: Agent Class
- Coverage=20
- Domain: none
- Range: LocationPeriodOrJurisdiction (recommended controlled vocabulary =
like Thesaurus of Geographic Names (TGN))
- Creator=20
- Domain: none
- Range: Agent Class
- Date=20
- Domain: none
- Range: Literal (recommended W3CDTF profile of ISO 8601)
- Format=20
- Domain: none
- Range: MediaTypeOrExtent (Recommended list of internet media types (MIM=
E)).
- Identifier=20
- Domain: none
- Range: Literal
- Language=20
- Domain: none
- Range: LinguisticSystem (Recommended RFC 4646 IETF standard)
- Publisher=20
- Domain: none
- Range: Agent
- Relation=20
- Domain: none
- Range: none (YET)
- Note: This term is intended to be used with NON-LITERAL values. As of D=
ecember 2007, the DCMI Usage board is seeking a way to express this intenti=
on with a formal range declaration.
- Rights=20
- Domain: none
- Range: RightsStatement
- Source=20
- Domain: none
- Range: none (YET)
- Note: This term is intended to be used with NON-LITERAL values. As of D=
ecember 2007, the DCMI Usage board is seeking a way to express this intenti=
on with a formal range declaration.
- Subject=20
- Domain: none
- Range: none (YET) For spatial or temporal topic of the resource, use th=
e Coverage element instead.
- Note: This term is intended to be used with NON-LITERAL values. As of D=
ecember 2007, the DCMI Usage board is seeking a way to express this intenti=
on with a formal range declaration.
- Title=20
- Domain: none
- Range: Literal
- Type=20
- Domain:none
- Range: Any Class? (reference needed) (Recommended usage is the DCMI Typ=
e Vocabulary (DCMIType). For file format, physical medium or dimensions: us=
e format!
New properties
Following properties are recent and haven't been part of the standard DS=
pace metadata schema. However, some of these overlap with other properties =
in DSpace
- Abstract=20
- Domain: none
- Range: none
- Possible DSpace overlap: dc.description.abstract
- accessRights=20
- Domain: none
- Range: RightsStatement
- Possible DSpace overlap: ....... (to add)
- accrualMethod=20
- Domain: Collection
- Range: MethodOfAccrual
- Possible DSpace overlap: none?
- accrualPeriodicity=20
- Domain: Collection
- Range: Frequency
- Possible DSpace overlap: none?
- accrualPolicy=20
- Domain: Collection
- Range: Policy
- Possible DSpace overlap: collection policies?
- alternative=20
- Domain: none
- Range: Literal
- Possible DSpace overlap: dc.title.alternative
- audience=20
- Domain: none
- Range: AgentClass
- Possible DSpace overlap: none?
- available=20
- Domain: none
- Range: Literal
- Possible DSpace overlap: dc.date.available
- bibliographicCitation - INTERESTING ONE
- Domain: BibliographicResource
- Range: Literal
- Possible DSpace overlap: dc.identifier.citation
- conformsTo=20
- Domain: none
- Range: Standard
- Possible DSpace overlap: none?
- created=20
- Domain: none
- Range: Literal
- Possible DSpace overlap: dc.date.created
- dateAccepted=20
- Domain:none
- Range: Literal
- Possible DSpace overlap: none?
- dateCopyrighted=20
- Domain:none
- Range: Literal
- Possible DSpace overlap: embargo solutions?
- dateSubmitted=20
- Domain:none
- Range: Literal
- Possible DSpace overlap: dc.date.submitted
- educationLevel=20
- Domain:none
- Range:AgentClass
- Possible DSpace overlap: none?
- extent=20
- Domain:none
- Range: SizeOrDuration
- Possible DSpace overlap: dc.format.extent
- hasFormat=20
- Domain: none
- Range: none (YET)
- Note: This term is intended to be used with NON-LITERAL values. As of D=
ecember 2007, the DCMI Usage board is seeking a way to express this intenti=
on with a formal range declaration.
- Possible DSpace overlap: none?
- hasPart=20
- Domain: none
- Range: none (YET)
- Note: This term is intended to be used with NON-LITERAL values. As of D=
ecember 2007, the DCMI Usage board is seeking a way to express this intenti=
on with a formal range declaration.
- Possible DSpace overlap: dc.relation.haspart
- hasVersion=20
- Domain: none
- Range: none (YET)
- Note: This term is intended to be used with NON-LITERAL values. As of D=
ecember 2007, the DCMI Usage board is seeking a way to express this intenti=
on with a formal range declaration.
- Possible DSpace overlap: dc.relation.hasversion
- instructionalMethod=20
- Domain: none
- Range: MethodOfInstruction
- Possible DSpace overlap: none?
- isFormatOf=20
- Domain: none
- Range: none (YET)
- Note: This term is intended to be used with NON-LITERAL values. As of D=
ecember 2007, the DCMI Usage board is seeking a way to express this intenti=
on with a formal range declaration.
- Possible DSpace overlap: dc.relation.isformatof
- isPartOf=20
- Domain: none
- Range: none (YET)
- Note: This term is intended to be used with NON-LITERAL values. As of D=
ecember 2007, the DCMI Usage board is seeking a way to express this intenti=
on with a formal range declaration.
- Possible DSpace overlap: dc.relation.ispartof
- isReferencedBy=20
- Domain: none
- Range: none (YET)
- Note: This term is intended to be used with NON-LITERAL values. As of D=
ecember 2007, the DCMI Usage board is seeking a way to express this intenti=
on with a formal range declaration.
- Possible DSpace overlap: dc.relation.isreferencedby
- isReplacedBy=20
- Domain: none
- Range: none (YET)
- Note: This term is intended to be used with NON-LITERAL values. As of D=
ecember 2007, the DCMI Usage board is seeking a way to express this intenti=
on with a formal range declaration.
- Possible DSpace overlap: dc.relation.isreplacedby
- isRequiredBy=20
- Domain: none
- Range: none (YET)
- Note: This term is intended to be used with NON-LITERAL values. As of D=
ecember 2007, the DCMI Usage board is seeking a way to express this intenti=
on with a formal range declaration.
- Possible DSpace overlap: none?
- issued=20
- Domain: none
- Range: Literal
- Possible DSpace overlap: dc.date.issued
- isVersionOf=20
- Domain: none
- Range: none (YET)
- Note: This term is intended to be used with NON-LITERAL values. As of D=
ecember 2007, the DCMI Usage board is seeking a way to express this intenti=
on with a formal range declaration.
- Possible DSpace overlap: dc.relation.isversionof
- license TRICKY ONE
- Domain: none
- Range: LicenseDocument
- Possible DSpace overlap: item license
- mediator=20
- Domain: none
- Range: AgentClass
- Possible DSpace overlap: none?
- medium=20
- Domain: PhysicalResource
- Range: PhysicalMedium
- Possible DSpace overlap: dc.format.medium
- modified=20
- Domain: none
- Range: Literal
- Possible DSpace overlap: dc.date.updated (wasn't there a dc.date.modifi=
ed????)
- provenance=20
- Domain: none
- Range: ProvenanceStatement
- Possible DSpace overlap: dc.description.provenance
- references=20
- Domain: none
- Range: none (YET)
- Note: This term is intended to be used with NON-LITERAL values. As of D=
ecember 2007, the DCMI Usage board is seeking a way to express this intenti=
on with a formal range declaration.
- Possible DSpace overlap: dc.citation ????????????
- replaces=20
- Domain: none
- Range: none (YET)
- Note: This term is intended to be used with NON-LITERAL values. As of D=
ecember 2007, the DCMI Usage board is seeking a way to express this intenti=
on with a formal range declaration.
- Possible DSpace overlap: dc.relation.replaces
- requires=20
- Domain: none
- Range: none (YET)
- Note: This term is intended to be used with NON-LITERAL values. As of D=
ecember 2007, the DCMI Usage board is seeking a way to express this intenti=
on with a formal range declaration.
- Possible DSpace overlap: dc.relation.requires
- rightsHolder=20
- Domain: none
- Range: Agent
- Possible DSpace overlap: dc.rights.holder
- spatial=20
- Domain: none
- Range: Location
- Possible DSpace overlap: dc.coverage.spatial
Possible Approaches
Adding a new schema dcterms that lives next to the standard dc sche=
ma
Pro
- Possibly easier to ensure backwards compatibility, as we're not touchin=
g the standard schema.
- ...
Con
------=_Part_28495_805786837.1711647877619--