Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

identifier 2.0 #49

Closed
stansmith907 opened this issue Aug 23, 2016 · 3 comments
Closed

identifier 2.0 #49

stansmith907 opened this issue Aug 23, 2016 · 3 comments
Labels
enhancement Improve or modify an existing feature
Milestone

Comments

@stansmith907
Copy link
Contributor

stansmith907 commented Aug 23, 2016

The new MD_Identifier combines the MD_Identifier and RS_Identifier (i.e. used in imageQuality and other places in -2). I have combined the two so only a single form is supported in mdJson 2.0.

Changes:

  1. “identifier” (or “code” in ISO) is a scalar of type character string. Definition: “alphanumeric value identifying an instance in the namespace.”
  2. “namespace” (or “codeSpace” in ISO) is a scalar of type character string. Definition: “identifier or namespace in which the code is valid.”
  3. “version” is a scalar of type character string. Definition: “version identifier for the namespace”.
  4. “description” is a scalar of type character string. Definition: “natural language description of the meaning of the code value.” We can use this attribute to replace the “type” attribute in mdJson 1.0.
  5. “authority” is an abbreviated citation object. Definition: “the person or party responsible for maintenance of that namespace.” I limited the number of citation attributes in mdJson 2.0 (as we did in 1.0). Issue authority 2.0 #54.
  6. "type" element was dropped in mdJson 1.0. It was internal only to mdJson and had no output in -2 or -1. "description" is adequate to handle "type" if necessary.
{
   "identifier": "",
   "namespace": "",
   "version": "",
   "description": "",
   "authority": {
      "see": "citation 2.0"
   }
}

see XML example citation -3.xml

@stansmith907 stansmith907 added the enhancement Improve or modify an existing feature label Aug 23, 2016
@jlblcc jlblcc modified the milestone: 2.0 Aug 23, 2016
@jlblcc
Copy link
Member

jlblcc commented Oct 14, 2016

We need type. It was being used to specifically identify, well, the type. I believe we're also using it to id ISBN and ISSN in -2, since those are actual elements. Beyond that, we need it to id DOI's and such. It should probably be backed by a codelist of suggested types.

@stansmith907
Copy link
Contributor Author

I was thinking type would fit in namespace, I think they are the same thing. Namespace is a simple character string, not a URI, which would be placed within authority. Perhaps calling it codeSpace as it is in ISO would help. But there were objections to using that name when designing mdJson 1.0.

@jlblcc
Copy link
Member

jlblcc commented Oct 15, 2016

OK, I stand corrected. We'll need to make sure that we indicate that the "official" namespace should be used when one exists, like:

  • urn:ISBN
  • urn:ISSN
  • info:doi/
  • info:ark/

jlblcc added a commit that referenced this issue Jan 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improve or modify an existing feature
Projects
None yet
Development

No branches or pull requests

2 participants