- DCTermsChangesActionsDone

Changes made to DCTERMS definitions and comments

Changes made in: DCTermsChanges

Removed "qualifies" statements from encoding schemes descriptions, as such relationships are declared in application profiles only, not in term declarations.
Audience
Alternative
TableofContents
Abstract
Created
Valid
Available
Issued
Modified
Extent
Medium
IsVersionOf
HasVersion
IsReplacedBy
Replaces
IsRequiredBy
Requires
IsPartOf
HasPart
IsReferencedBy
References
IsFormatOf
HasFormat
conformsTo
spatial
temporal
mediator
dateAccepted
dateCopyrighted
dateSubmitted
educationLevel
accessRights
bibliographicCitation
license
rightsHolder
provenance
instructionalMethod
accrualMethod ("uses a controlled vocabulary" removed from comment)
accrualPeriodicity ("uses a controlled vocabulary" removed from comment)
accrualPolicy ("uses a controlled vocabulary" removed from comment)
LCSH
MESH
DDC
LCC
UDC
DCMIType
IMT
ISO639-2
RFC1766
URI
Point
ISO3166
Box
TGN
Period
W3CDTF
RFC3066
NLM
RFC4646 (new term)
dcterms:creator rdfs:subPropertyOf dcterms:contributor
dcterms:source rdfs;subPropertyOf dcterms:relation

Extent=(need to correct comment)=ok - heh?
Note ACTION: do a which hunt Tom
If promoting interoperability is interpreted as meaning that we maintain the encoding schemes already in our namespace, then we will occasionally add new terms in order to keep our term set up to date.
ISSUE: we recognize a set of concepts for language, however, interpreting the ISO639-2 as a set of concepts would break the namespace policy because ISO639-2 is a set of strings (defined by ISO and us).
ISSUE: because of the way RFCs work, they change and take on a different number

Removed