adiwg / mdJson-schemas

JSON schemas, examples, and templates for ADIwg metadata standards
http://www.adiwg.org/projects/
GNU Lesser General Public License v3.0
18 stars 15 forks source link

mdJson metadata object required #188

Open stansmith907 opened 6 years ago

stansmith907 commented 6 years ago

Maybe. Currently at the top schema level only the schema and contact objects are required. It seems the metadata object should also be required - at least if the record is being sent through the translator. I can see saving an mdJson object with just contacts for the mdEditor, but that should never be passed to the mdTranslator. From an mdTranslator perspective there should always be a metadata object, thus the schema should back that up.

jlblcc commented 6 years ago

I can implement this now, but we did discuss the possibility of just having a dataDictionary, i.e. for ISO 19110 output. Do we want to revisit that or just require metadata only?

stansmith907 commented 6 years ago

Yep, you're right forgot about dictionary only option. Close this one.

jlblcc commented 6 years ago

We can require at least one of dataDictionary or metadata?

stansmith907 commented 6 years ago

Unless we also want to just hold a bundle of contacts. Although that may not be of any value to the translator, the editor may also want to use the schema. We can just leave it as is for the schema and this can be a translator check only.