Difference between revisions of "Talk:NSDL Registry Functional Requirements"
From Metadata-Registry
| Line 4: | Line 4: | ||
#*Need definition of "agency"--we used "responsible entity" for CRS | #*Need definition of "agency"--we used "responsible entity" for CRS | ||
#*May need agent "roles" for authentication and maintenance? | #*May need agent "roles" for authentication and maintenance? | ||
| − | |||
#Persistence and Versioning | #Persistence and Versioning | ||
#*Need policy definition for editorial changes vs changes that require new versions of an element or term (Similar to DCMI?) | #*Need policy definition for editorial changes vs changes that require new versions of an element or term (Similar to DCMI?) | ||
#*Do we need to know when instance data exists referencing some categories of registered information? | #*Do we need to know when instance data exists referencing some categories of registered information? | ||
| − | |||
#Notification | #Notification | ||
#*Allow registration of usage as well as responsibility, so that certain kinds of changes go out to a user community? | #*Allow registration of usage as well as responsibility, so that certain kinds of changes go out to a user community? | ||
Latest revision as of 05:45, 9 September 2005
Policy Needs
- Definitions
- Need definition of "agency"--we used "responsible entity" for CRS
- May need agent "roles" for authentication and maintenance?
- Persistence and Versioning
- Need policy definition for editorial changes vs changes that require new versions of an element or term (Similar to DCMI?)
- Do we need to know when instance data exists referencing some categories of registered information?
- Notification
- Allow registration of usage as well as responsibility, so that certain kinds of changes go out to a user community?
