Difference between revisions of "DCLibApplicationProfile"
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
relationship between two items | relationship between two items | ||
* source ? | * source ? | ||
== properties == | |||
* any property with a literal value can be typed | |||
* we use legacy namespace for all creator, contributor and publisher | |||
* we use legacy namespace for subject | |||
* we use EDTF for data, but nor for modified, copyright, submitted accepted | |||
* we need the legacy namespace for type | |||
* we change the examples resp. links for type vocabularies (C. Harper) | |||
* we need a proposal to the Usage Board to change the range of extent (S. Ruehle) | |||
* we have to change the comment for identifiers (J. Hakala) | |||
* we need a clear distinction between identifiers for items and identifiers for "bibliographic resources" | |||
* we write some best practice how to use the legacy namespace with non-literals | |||
== date == | == date == | ||
EDTF standard | EDTF standard | ||
Revision as of 19:38, 20 October 2010
DC Lib AP[edit]
Scope of the DC Lib AP[edit]
- text-material (published and unpublished)
- monographs
- continuing material(journal,yearbook)
- articles
- grey literatur
- websites (sometimes monographs, sometimes continuing material)
- transcripts
entity relationship model[edit]
- "bibliographic resource
- item
relationship between two items
- source ?
properties[edit]
- any property with a literal value can be typed
- we use legacy namespace for all creator, contributor and publisher
- we use legacy namespace for subject
- we use EDTF for data, but nor for modified, copyright, submitted accepted
- we need the legacy namespace for type
- we change the examples resp. links for type vocabularies (C. Harper)
- we need a proposal to the Usage Board to change the range of extent (S. Ruehle)
- we have to change the comment for identifiers (J. Hakala)
- we need a clear distinction between identifiers for items and identifiers for "bibliographic resources"
- we write some best practice how to use the legacy namespace with non-literals
date[edit]
EDTF standard