Git Product home page Git Product logo

Comments (5)

stansmith907 avatar stansmith907 commented on July 4, 2024

In making this recommendation I made a few assumptions we should review be implementing:

  • I changed "parentMetadataIdentifier" to "parentMetadata" which not only better matches naming for 19115-1 (which is not really important) but parent metadata is now a citation not an identifier. As a citation identifier is not required.
  • I removed authority (citation) from "metadataIdentifier". I thought these citation fields would overlap with similar "metadataInfo" section fields and cause confusion. This is just an identifier for the metadata record.
  • I also removed authority from the identifier section of "parentMetadata". Seems like a citation inside a citation to identify the metadata record for a parent work or program was too much. The authority would be describing the entity that created the identifier.

Proposal:

    "metadata": {
        "metadataInfo": {
            "metadataIdentifier": {
                "identifier": "",
                "type": ""
            },
            "parentMetadata": {
                "title": "",
                "date": [
                    {
                        "date": "0000-00-00",
                        "dateType": ""
                    }
                ],
                "edition": "",
                "responsibleParty": [
                    {
                        "contactId": "",
                        "role": ""
                    }
                ],
                "presentationForm": [""],
                "identifier": [
                    {
                        "identifier": "",
                        "type": ""
                    }
                ],
                "onlineResource": [
                    {
                        "uri": "http://thisisanexample.com",
                        "protocol": "",
                        "name": "",
                        "description": "",
                        "function": ""
                    }
                ]
            },
            "metadataScope": [""],

from mdjson-schemas.

dwalt avatar dwalt commented on July 4, 2024

I agree with the naming change. I also agree that removing authority is
probably a good idea as it seems to add verbosity and circular references
that I'm not sure adds much value.

On Wed, Sep 17, 2014 at 10:10 AM, stansmith907 [email protected]
wrote:

In making this recommendation I made a few assumptions we should review be
implementing:

  • I changed "parentMetadataIdentifier" to "parentMetadata" which not
    only better matches naming for 19115-1 (which is not really important) but
    parent metadata is now a citation not an identifier. As a citation
    identifier is not required.
  • I removed authority (citation) from "metadataIdentifier". I
    thought these citation fields would overlap with similar "metadataInfo"
    section fields and cause confusion. This is just an identifier for the
    metadata record.
  • I also removed authority from the identifier section of
    "parentMetadata". Seems like a citation inside a citation to identify the
    metadata record for a parent work or program was too much. The
    authority would be describing the entity that created the identifier.

Proposal:

"metadata": {
    "metadataInfo": {
        "metadataIdentifier": {
            "identifier": "",
            "type": ""
        },
        "parentMetadata": {
            "title": "",
            "date": [
                {
                    "date": "0000-00-00",
                    "dateType": ""
                }
            ],
            "edition": "",
            "responsibleParty": [
                {
                    "contactId": "",
                    "role": ""
                }
            ],
            "presentationForm": [""],
            "identifier": [
                {
                    "identifier": "",
                    "type": ""
                }
            ],
            "onlineResource": [
                {
                    "uri": "http://thisisanexample.com",
                    "protocol": "",
                    "name": "",
                    "description": "",
                    "function": ""
                }
            ]
        },
        "metadataScope": [""],


Reply to this email directly or view it on GitHub
#21 (comment)
.

from mdjson-schemas.

jlblcc avatar jlblcc commented on July 4, 2024

I'm fine with this. Note, that the schema will still allow the "authority" sections.

from mdjson-schemas.

jlblcc avatar jlblcc commented on July 4, 2024

Can we close this?

from mdjson-schemas.

stansmith907 avatar stansmith907 commented on July 4, 2024

I think so. It's implemented in the translator and schema.

from mdjson-schemas.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.