Comments (5)
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.
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.
I'm fine with this. Note, that the schema will still allow the "authority" sections.
from mdjson-schemas.
Can we close this?
from mdjson-schemas.
I think so. It's implemented in the translator and schema.
from mdjson-schemas.
Related Issues (20)
- New Class - ProcessParameter HOT 1
- Acquisitions HOT 1
- New Class - CoverageResult HOT 5
- Data Quality
- New Class - ComponentIdentifier HOT 1
- Feature/Data Quality HOT 6
- Identifying metadata standard and profile
- Verify translation descriptions for dataQuality report elements HOT 3
- Update dataQuality report type element
- Verify and update datQuality derivedElementReport schema HOT 2
- Update dataQuality report evaluationMethod element HOT 2
- Rename dev --> develop HOT 1
- Release v2.8.2 HOT 1
- Update Ruby Gem Version Number
- DQ_CompletenessOmission Typo
- Missing DQ_NonQuantitativeAttributeAccuracy
- Release v2.8.3 HOT 1
- Bug Fix Data Quality and Schema Versioning
- Fix Data Quality Report Type Enum
- Update definitions for mdJSON component system identifiers
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mdjson-schemas.