Skip to content
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

Validator (Editor). Wrongly gives error for summary element when child of info. #97

Open
JohnLukeBentley opened this issue Mar 31, 2018 · 1 comment

Comments

@JohnLukeBentley
Copy link

JohnLukeBentley commented Mar 31, 2018

To reproduce:

Line 15: Element “summary” from namespace “http://purl.org/net/xbiblio/csl” not allowed as child of element “info” from namespace “http://purl.org/net/xbiblio/csl” in this context. (Suppressing further errors from this subtree.)

However, summary is permitted as a child of info. This is demonstrated in the example in the "Getting Started" section of https://juris-m.github.io/editor/ (as well as being in the spec http://docs.citationstyles.org/en/stable/specification.html)

Continue the test ...

  • In your local copy of jlb-jm-indigobook.csl remove the summary element (the whole line).
  • Reupload to the Validator and Load.
  • Observe "Success and welcome".

The *.csl file appears to the validator as otherwise OK.

Continue the test ...

  • Load/validate a local default copy of jm-harvard-australian-national-university.csl
  • Observe this passes even though it has a summary child element of info.

It seems that the Validator doesn't like the summary element, but only in some circumstances which my jlb-jm-indigobook.csl triggers.

Maybe the Validator is choking on my comments? Search for <!-- JLB Start -->. Or perhaps the particulars of the text in my summary

Modifies JM Indigo Book by outputing ISO 8601 date formats. E.g. "2018-03-24".

??

Tested in Firefox 59.0.2

Edit: " appears the validator" to "appears to the validator"; "chocking" to "choking"; markup for formatting consistency.

@fbennett
Copy link
Contributor

fbennett commented Mar 31, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants