Case element content from the OPS namespace
| Project: | EPUB Maintenance |
| Component: | Open Publication Structure (OPS) |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | open |
Jump to:
Section 2.6.3.1.2: case Element says "The case element contains no content from the OPS namespace.", but the OPS schema uses this pattern inside case:
<zeroOrMore>
<ref name="OPS.switch"/>
</zeroOrMore>
Meaning that the switch element (which is inside the OPS namespace) is allowed. So something is clearly wrong here.
Description
Issue Id:
56
Resolution:
Insert resolution here.
- Login to post comments
Comments
#1
To my read, the two instances of zerOfMore OPS:switch references (inside ops:case and ops:default) in the OPS.switch definition seems wrong, but not insane -- as Brady points out, perfectly valid in most programming languages. And, as Peter pointed out it's the only real way to do "and"s.
Brady, Peter, Makoto -- please chime in.
Like the other ops:switch open issue, this could be fixed (if it's a bug) with an errata, or moved to future consideration pending the direction that ops:switch will take in EPUB3.
#2
I think in this case the spec language is in error. What's wrong in having switch inside case? What if you want to use both MathML and ChemML, how else are you going to express that?
#3
Yup - I agree with Peter.
#4
Yea, just edited my response to reflect that! :-)
But, still looking for errata versus future consideration opinions.
#5
This defect has to be fixed by revising the prose.