[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Ambiguous content model in DITA 2.0
I agree with Robert’s analysis—his proposed change looks like the right one to me. Cheers, E. _____________________________________________ Eliot Kimber Sr Staff Content Engineer O: 512 554 9368 M: 512 554 9368 LinkedIn | Twitter | YouTube | Facebook From:
dita@lists.oasis-open.org <dita@lists.oasis-open.org> on behalf of Robert Anderson <robert.dan.anderson@oracle.com> [External Email] Hi everyone, Passing along a reported issue in the grammar files for TC discussion. Thanks, Robert From: Patrick Baker <pbaker@stilo.com> Hi Robert, According to OmniMark, the following content model is ambiguous: <!ENTITY % messagepanel.content A content model must not be ambiguous. For the declared element "messagepanel", the element "howtoavoid" is ambiguous in the content model. The fix would be straight forward... Just change one * to a +. It will match the same XML, but will not be ambiguous. <!ENTITY % messagepanel.content I'd recommend a similar change in the RNG. regards, Patrick |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]