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, -- Florent Georges http://www.fgeorges.org/
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,
Sorin Ristache wrote:
I would not say it is a bug. Should all the example XML files be error free?
Oh, no. I just thought that was a bug and reported it, but it could be a feature, sure (maybe an extra comment in the XML instance to make that clear would be useful?) Regards, -- Florent Georges http://www.fgeorges.org/
We added an XML comment in both sample files called tournament.xml (in the schematron/iso folder and the schematron/1.5 one) about the validation errors reported by the embedded Schematron constraints. Thank you for your suggestion, Sorin Florent Georges wrote:
Sorin Ristache wrote:
I would not say it is a bug. Should all the example XML files be error free?
Oh, no. I just thought that was a bug and reported it, but it could be a feature, sure (maybe an extra comment in the XML instance to make that clear would be useful?)
Sounds like a useful example to me! Don't remove it, please... Maybe it would be helpful though to forestall confusion by putting a comment in the XML file (if there's not one already) explaining that the data intentionally violates a Schematron constraint for demonstration purposes. Lars On 10/27/2008 5:23 AM, Sorin Ristache wrote:
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 oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user X-Quarantine ID /var/spool/MD-Quarantine/06/qdir-2008-10-27-06.30.07-001
participants (3)
-
Florent Georges -
Lars Huttar -
Sorin Ristache