Hello,
It is an example that demonstrates Schematron constraints that cannot be
expressed in a RELAX NG schema or a W3C XML Schema schema and how Oxygen
reports the violations of such constraints: the type of constraint (ISO
Schematron), the XSLT version of the constraint (XSLT 2.0) and the
diagnostics message. I would not say it is a bug. Should all the example
XML files be error free?
Regards,
Sorin
Florent Georges wrote:
Hi
I have intalled the new oXygen 10, and the sample XML file
schematron/iso/tournament/Tournament.xml contains:
<Type>Singles</Type>
<Date>2001-03-20</Date>
<Participants nbrParticipants="3">
<Name id="p1">Nick</Name>
<Name id="p2">Marcus</Name>
<Name id="p3">Eddie</Name>
</Participants>
<Teams nbrTeams="5">
<Team id="t1" Name="Team 1">
<Member>p1</Member>
</Team>
<Team id="t2" Name="Team 2">
<Member>p2</Member>
</Team>
<Team id="t3" Name="Team 3">
<Member>p3</Member>
</Team>
</Teams>
You can see that Teams/@nbrTeams eq 5, while there is only 3 Team
elements. This is actually caught by the associated Schematron schema,
by the assert:
../t:Participants/@nbrParticipants = ../t:Teams/@nbrTeams
Seems like a bug?
Regards,
_______________________________________________
oXygen-user mailing list
[email protected]
http://www.oxygenxml.com/mailman/listinfo/oxygen-user
