Re: [jats-list] Strange top-level elements permitted in the RNG version of Blue

["Imsieke, Gerrit, le-tex gerrit.imsieke@xxxxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Ah ok, thank you! Then maybe someone already removed them manually for 
Pumpkin.

I noticed this because I wrote some XSLT that identifies the *reachable* 
elements in the RNG versions of the customizations. They contain all the 
models that the original DTD provides, and there is no information 
retained in the RNG which model was in fact activated or deactivated by 
means of parameter entities in the DTD.

Gerrit

On 26.09.2020 14:33, Jacques Legare jlegare@xxxxxxxxx wrote:
> I can't be sure in this specific case, but I know this happens if a 
> Relax NG schema is generated using TRANG and there are unreachable 
> elements in the DTD. They end up getting thrown into the start set for 
> the schema.
>
> On Sat, Sep 26, 2020 at 6:14 AM Imsieke, Gerrit, le-tex 
> gerrit.imsieke@xxxxxxxxx <mailto:gerrit.imsieke@xxxxxxxxx> 
> <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx 
> <mailto:jats-list-service@xxxxxxxxxxxxxxxxxxxxxx>> wrote:
>
>     I discovered that the Relax NG schemas of the Publishing (Blue)
>     customization permit top-level elements that are not part of Blue:
>
>     <start>
>      B  B <choice>
>      B  B  B <ref name="article"/>
>      B  B  B <ref name="rp"/>
>      B  B  B <ref name="overline-start"/>
>      B  B  B <ref name="unstructured-kwd-group"/>
>      B  B  B <ref name="underline-end"/>
>      B  B  B <ref name="underline-start"/>
>      B  B  B <ref name="x"/>
>      B  B  B <ref name="overline-end"/>
>      B  B </choice>
>     </start>
>
>     In the Green and Pumpkin RNG schemas, there's only this:
>
>     <start>
>      B  B <choice>
>      B  B  B <ref name="article"/>
>      B  B </choice>
>     </start>
>
>     I haven't checked all 4 variants of each customization, I only took two
>     samples each.
>
>     Is there a reason for this, or did this happen by mistake?
>
>     Gerrit