Closed doulikecookiedough closed 3 months ago
The proposed formatID does not resolve to the schema. How about using a fragment id instead, so that it resolves? In addition, there is nothing specific about this format for HashStore -- so I recommend we remove all signs of that. The media type text/xml
is fine, as defined in RFC 7303. Finally, the extension for xml files is generally xml
. So I propose:
https://ns.dataone.org/service/types/v2.0#SystemMetadata
Thank you @mbjones and @taojing2002 for helping to resolve/address this issue!
Format Metadata
Provide the standard metadata for the proposed format, ensuring that the id and name are unique and appropriate to the version of the format being proposed.
http://ns.dataone.org/service/types/v2.0:SystemMetadata
System Metadata (HashStore)
METADATA
text/xml
None
Format description
With the
Metacat
back-end storage refactor, we will need a new metadata format to represent the metadata that corresponds to each data object in theHashStore
. Development is ongoing and this issue should be updated as discussions take place and progress is made.Specification / Namespace documentation
The format will be defined at
http://ns.dataone.org/service/types/v2.0:SystemMetadata
.Checklist
image/png
is specific to one format, whereastext/xml
is not specific to one format)DATA
,METADATA
, orRESOURCE
Considerations
mediaType
. As of writing this issue, I believe that this metadata will be an.xml
document.formatName
- isSystem Metadata (HashStore)
ok?