Closed taojing2002 closed 3 months ago
@taojing2002 How about a fragmentID so the namespace resolves:
I also updated the name to remove the DataONE
, and switched to a hash symbol in the formatID.
I also think the format should use DataONE V2 namespaces. So the final would be:
http://ns.dataone.org/service/types/v2.0#ObjectFormatList
Object Format List
METADATA
text/xml
xml
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/v1#ObjectFormatList
Object Format List
METADATA
text/xml
xml
Format description
When we install a new CN, we should insert the object which contains the list of object formats first before it functions. Currently we use the old Metacat API to insert/update it and the object is treated as a metadata object. However, after we disable the old Metacat API, we should use DataONE
cn.create
to insert the documents. If we don't have an object format identifier, which is a metadata type, for this object, CN will treat it as a data object.Specification / Namespace documentation
The namespace is http://ns.dataone.org/service/types/v1
Provide the location(s) of the documentation of the format specification or the namespace for the format or vocabulary.
Checklist
image/png
is specific to one format, whereastext/xml
is not specific to one format)DATA
,METADATA
, orRESOURCE
Considerations
Describe or list any considerations that might impact the use of the format, or related issues that we should consider.