-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mdJson metadata object required #188
Comments
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? |
Yep, you're right forgot about dictionary only option. Close this one. |
We can require at least one of dataDictionary or metadata? |
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. |
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.
The text was updated successfully, but these errors were encountered: