We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
EML validation imposes additional constraints beyond the XML schema validation. I believe these can be summarized as follows:
id
<references>
<describes>
annotation
eml_validate() should enforce both of these conditions as well. (Should be possible as simple xpath?)
eml_validate()
Migrated from ropensci/EML#244.
The text was updated successfully, but these errors were encountered:
The validation rules in EML are now clearly listed here: https://github.com/NCEAS/eml/blob/BRANCH_EML_2_2/docs/eml-validation-refs.md
That document will be part of the EML 2.2.0 release specification.
Sorry, something went wrong.
closed by #26
No branches or pull requests
EML validation imposes additional constraints beyond the XML schema validation. I believe these can be summarized as follows:
id
+system attributes on any element should be unique.<references>
/<describes>
and an attribute calledid
.annotation
needs a subject: either from theid
of its parent or as a child<references>
of the annotation, but not both!eml_validate()
should enforce both of these conditions as well. (Should be possible as simple xpath?)Migrated from ropensci/EML#244.
The text was updated successfully, but these errors were encountered: