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

Incorrect "may contain" text for anyElement #396

Open
hcayless opened this issue Oct 2, 2019 · 1 comment
Open

Incorrect "may contain" text for anyElement #396

hcayless opened this issue Oct 2, 2019 · 1 comment
Assignees
Labels
conversion: odd resp: council resp: StylesheetsGroup Issue is suitable for the group-learning approach taken in the Stylesheets Coop Working Group. status: needsDiscussion Council has not yet been able to agree on how to proceed. type: bug A bug report.

Comments

@hcayless
Copy link
Member

hcayless commented Oct 2, 2019

Elements that have <anyElement> in their content model, e.g. egXML and xenoData have the message "Character data only" in their "May contain" section. This must be a bug in the tagdocs processing. We probably never noticed it when Pure ODD came out.

@hcayless hcayless changed the title Incorrect "may contain" text for anyXML Incorrect "may contain" text for anyElement Oct 2, 2019
@hcayless hcayless self-assigned this Oct 2, 2019
hcayless added a commit that referenced this issue Oct 2, 2019
@sydb sydb added type: bug A bug report. resp: council resp: StylesheetsGroup Issue is suitable for the group-learning approach taken in the Stylesheets Coop Working Group. labels Mar 14, 2020
@sydb
Copy link
Member

sydb commented Mar 16, 2020

Oops.

  1. This is not a good ticket for Stylesheets group, as @hcayless has already fixed it (in 7b254fb)
  2. However, Council should re-visit the use of the output “ANY”, which is being generated (in common/common_tagdocs.xsl at ~2922) whenever there is a descendant <anyElement>. But the descendant <anyElement> may well have a @require, so it is not really the case that ANY element is allowed. Furthermore, the <anyElement> may have a sibling (either within <sequence> or <alternate> — note that all our cases are actually <alternate>) that allows elements from a namespace other than the one(s) required by the <anyElement>, which we would have to take account of in the output.

@peterstadler peterstadler added status: needsDiscussion Council has not yet been able to agree on how to proceed. conversion: odd labels May 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conversion: odd resp: council resp: StylesheetsGroup Issue is suitable for the group-learning approach taken in the Stylesheets Coop Working Group. status: needsDiscussion Council has not yet been able to agree on how to proceed. type: bug A bug report.
Projects
None yet
Development

No branches or pull requests

3 participants