Difference between revisions of "General Use Case Information"

From Metadata-Registry
Jump to: navigation, search
(Policies)
(Policies)
Line 35: Line 35:
 
*Maintainers are individuals and they must be associated with an Organization in order to maintain an Organization's schemas and schemes
 
*Maintainers are individuals and they must be associated with an Organization in order to maintain an Organization's schemas and schemes
 
*A Maintainer may be associated with more than one Organization and more than one schemas and schemes
 
*A Maintainer may be associated with more than one Organization and more than one schemas and schemes
*Maintainers assertion of association with an Organization will be assumed to be valid unless the organization, after notification of a schema or scheme publication, questions the association. In other words, Organizations don't need to specifically authorize individual Maintainers to maintain a specific scheme or schema, but reasonable measures will be taken to assure the Registry against fraud and error. <font color="red">Stuart: I still have <b>immense</b> problems with this since once a scheme or schema is published, it can only be deprecated and not removed.  Also, we promised in our supplemental answers to NSF that schemes and schemas will not be published without organizaitonal permission.  On page 8 we state: "All vocabularies registered (including the memberterms of those registered vocabularies) will be by permission of and (by the end of thesecond year of development) at the hands of the owners of those vocabularies."</font>
+
*Maintainers assertion of association with an Organization will be assumed to be valid unless the organization, after notification of a schema or scheme publication, questions the association. In other words, Organizations don't need to specifically authorize individual Maintainers to maintain a specific scheme or schema, but reasonable measures will be taken to assure the Registry against fraud and error. <font color="red">Stuart: I still have <b>immense</b> problems with this since once a scheme or schema is published, it can only be deprecated and not removed.  Also, we promised in our supplemental answers to NSF that schemes and schemas will not be published without organizational permission.  On page 8 we state: "All vocabularies registered (including the memberterms of those registered vocabularies) will be by permission of and (by the end of thesecond year of development) at the hands of the owners of those vocabularies."</font>
 
*Organizations must be able to be associated with an internet domain that will form the root of individual Vocabulary namespaces, or agree to allow the registry domain to substitute.
 
*Organizations must be able to be associated with an internet domain that will form the root of individual Vocabulary namespaces, or agree to allow the registry domain to substitute.

Revision as of 09:40, 9 October 2005

Actors

Human Actors

System Administrator
Overall system administrator. Responsible for system-level software and hardware maintenance
Registry Manager
Person (or persons) responsible for the administrative tasks involved in the management of a registry
Vocabulary Editor/Reviewer
Person (or persons) responsible for editorial functions related to submitted vocabularies
Visitor
Anyone viewing or browsing the site who is not logged in, including registered Maintainers who have not yet logged in.
Registered User
A Vistor who has registered himself/herself for the purpose of registering an organization or vocabulary. A Registered User may assume an additional role (Maintainer, Organization Contact) while registering an organization or vocabulary.
Organization Contact
Person acting on behalf of an organization, to whom notifications to the Organization may be sent.
Maintainer
Person responsible for maintaining a vocabulary

Non-human Actors

Registry
The registry software, including user interfaces, processing systems, and services
Service
An interface intended to be used by machines that provides data in response to a request
Service Consumer
Machine requesting data from a service
Organization
Basically a term for for group of persons or an educational or business unit rather than an individual. For instance, an NSDL Project is an organization. In the current context the organization is also the entity responsible for the vocabulary. Vocabularies are associated with an Organization and maintained by a Maintainer who is authorized by the Organization. (Policy question?)

Terms

Vocabulary
[Merriam-Webster] "a list or collection of words or of words and phrases usually alphabetically arranged and explained or defined" ; [In the context of this project] "A set of concepts, represented by words and word relationships, presented in a structured manner." [NOTE: the DC Abstract Model uses the term Vocabulary Encoding Scheme, defined as "A vocabulary encoding scheme is a class that indicates that the value of a property is taken from a controlled vocabulary (or concept-space), such as the Library of Congress Subject Headings"]
Hosted Vocabulary
A vocabulary whose canonical (official) version resides, or is "hosted" in the Registry.
Non-hosted Vocabulary
A vocabulary that is published (exposed) through the Registry but that is created and maintained by its promulgating agency in a separate registry or as a Web-addressable file in its own namespace.
Terms
DC Abstract Model "The generic name for a property (i.e. element or element refinement), vocabulary encoding scheme, syntax encoding scheme or concept taken from a controlled vocabulary (concept space)"
Tokens
[from Wikipedia] "In computer science, specifically lexical analysis, a token is usually a word or an atomic element within a string. Tokenizing is systematically replacing portions of a string by such corresponding token"
Simple Knowledge Organization System (SKOS)
[from SKOS Home Page] "SKOS is an area of work developing specifications and standards to support the use of knowledge organization systems (KOS) such as thesauri, classification schemes, subject heading lists, taxonomies, terminologies, glossaries and other types of controlled vocabulary within the framework of the semantic web"
PURLs
[from the OCLC PURL Home page] "A PURL is a Persistent Uniform Resource Locator. Functionally, a PURL is a URL. However, instead of pointing directly to the location of an Internet resource, a PURL points to an intermediate resolution service. The PURL resolution service associates the PURL with the actual URL and returns that URL to the client. The client can then complete the URL transaction in the normal fashion. In Web parlance, this is a standard HTTP redirect"

Vocabulary and Member Term States (Statuses?)

Draft
The state of a schema (element set) or a scheme (vocabulary and vocabulary terms) that has been created in the registry by a Maintainer but that has not been submitted to the Registry Manager (or delegate)
Submitted
The state of a schema (element set) or a scheme (vocabulary and vocabulary terms) that has been submitted by a Maintainer and is under review by the Regestry Manager (or delegate)
Published
The state of a schema (element set) or a scheme (vocabulary and vocabulary terms) that has been exposed to external human and machine agents through the registry
Deprecated
The state of a schema (element set) or a scheme (vocabulary and vocabulary terms) the use of which is no longer advised, most often because it has been withdrawn or replaced.

Policies

WARNING - assumption alert!! Many of the use cases below make assumptions about yet-to-be-decided policies (as of 9/2005)

  • Schemas and schemes must be associated with an Organization that acts as the Entity responsible for the Vocabulary
  • Maintainers are individuals and they must be associated with an Organization in order to maintain an Organization's schemas and schemes
  • A Maintainer may be associated with more than one Organization and more than one schemas and schemes
  • Maintainers assertion of association with an Organization will be assumed to be valid unless the organization, after notification of a schema or scheme publication, questions the association. In other words, Organizations don't need to specifically authorize individual Maintainers to maintain a specific scheme or schema, but reasonable measures will be taken to assure the Registry against fraud and error. Stuart: I still have immense problems with this since once a scheme or schema is published, it can only be deprecated and not removed. Also, we promised in our supplemental answers to NSF that schemes and schemas will not be published without organizational permission. On page 8 we state: "All vocabularies registered (including the memberterms of those registered vocabularies) will be by permission of and (by the end of thesecond year of development) at the hands of the owners of those vocabularies."
  • Organizations must be able to be associated with an internet domain that will form the root of individual Vocabulary namespaces, or agree to allow the registry domain to substitute.