Published along with TEI P5 as part of its build process test suite
@@ -17,6 +19,14 @@Here we are testing the Schematron that tests for duplicate
+ atttribute defintions, i.e.
This
Note that because this element is not a member of any + model class nor in any other element’s content model, it + will probably not show up in an output schema, which is + a good thing, becase defining an attribute twice like + that is an error in at least RELAX NG and DTD.
+Here we are testing the Schematron that tests for duplicate
+ atttribute defintions, i.e.
This
Note that because this element is not a member of any + model class nor in any other element’s content model, it + will probably not show up in an output schema, which is + a good thing, becase defining an attribute twice like + that is an error in at least RELAX NG and DTD.
+Here we are testing the Schematron that tests for duplicate
+ atttribute defintions, i.e.
This
Note that because this element is not a member of any + model class nor in any other element’s content model, it + will probably not show up in an output schema.
+Here we are testing the Schematron that tests for duplicate
+ atttribute defintions, i.e.
This
Note that the
Note that because this element is not a member of any + model class nor in any other element’s content model, it + will probably not show up in an output schema, which is + a good thing, becase defining an attribute twice like + that is an error in at least RELAX NG and DTD.
+Here we are testing the Schematron that tests for duplicate
+ atttribute defintions, i.e.
This
Note that the
Note that because this element is not a member of any + model class nor in any other element’s content model, it + will probably not show up in an output schema, which is + a good thing, becase defining an attribute twice like + that is an error in at least RELAX NG and DTD.
+Here we are testing the Schematron that tests for duplicate
+ atttribute defintions, i.e.
This
Note that because this element is not a member of any + model class nor in any other element’s content model, it + will probably not show up in an output schema, which is + a good thing, becase defining an attribute twice like + that is an error in at least RELAX NG and DTD.
+