Skip to content
This repository has been archived by the owner on Nov 21, 2024. It is now read-only.

R28a: Provide guidance and clarification on use of source and version attributes. #32

Closed
pdpinch opened this issue Oct 11, 2010 · 2 comments

Comments

@pdpinch
Copy link

pdpinch commented Oct 11, 2010

Better documentation to associate the Element Version and Namespace attributes from the PBCore data dictionary with their implementation in the source and version attributes. (Allow a version attribute at PBCoreDescriptionDocument as it is currently tough to figure out what version of PBCore a document is). (Consider using SKOS or publication dates to version PBCore's recommended picklists to encourage more consistent referenece with PBCore records).

@MarcosSueiro
Copy link

Does this need to be a separate element, or can it be embedded (as in one field being PBCore 1.0 or PBCore 1.2 or whatever)?

@pdpinch
Copy link
Author

pdpinch commented Mar 3, 2011

We've addressed this in documentation.

Source is the human-readable name of the authority.
Version is a numerical version number
Ref is a URI that (hopefully) identifies uniquely both source and version.

Throughout the documentation we have recommended controlled vocabularies, and include their URI's in sample documentation.

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants