Difference between revisions of "Level 3 Schema and Schematron Feedback"
Jump to navigation
Jump to search
(→Tester: Enter Your Name: what Sebastian sent by email) |
(→Tester: Kevin Hawkins: hi@rend not valid) |
||
Line 3: | Line 3: | ||
==Tester: Kevin Hawkins== | ==Tester: Kevin Hawkins== | ||
− | * Most <elementSpec>s have examples that are taken exactly from P5 but do not validate according to the ODD itself. Furthermore, definitions sometimes refer to sections of P5 with pointers such as <code><ptr target="#SACR"/></code> , which don't | + | * Most <code>elementSpec</code>s have examples that are taken exactly from P5 but do not validate according to the ODD itself. Furthermore, definitions sometimes refer to sections of P5 with pointers such as <code><ptr target="#SACR"/></code> , which don't resolve. I recommend omitting all element definitions since creation and maintenance of these is too much for us to undertake. |
+ | * <code>hi</code> won't accept <code>rend</code> attribute. | ||
==Tester: Sebastian Rahtz== | ==Tester: Sebastian Rahtz== |
Revision as of 03:15, 30 June 2011
>>Return to testing instructions: Feedback_on_the_Best_Practices_for_TEI_in_Libraries_ODD_Documentation_and_Schemas
Tester: Kevin Hawkins
- Most
elementSpec
s have examples that are taken exactly from P5 but do not validate according to the ODD itself. Furthermore, definitions sometimes refer to sections of P5 with pointers such as<ptr target="#SACR"/>
, which don't resolve. I recommend omitting all element definitions since creation and maintenance of these is too much for us to undertake. hi
won't acceptrend
attribute.
Tester: Sebastian Rahtz
In an email, Sebastian wrote: surely & inside <egXML> is not intended?
Tester: Enter Your Name
Comments/Feedback
- List feedback, problems encountered, etc. in bulleted list form. Provide detailed examples please so that we may make corrections more easily.
- Feedback
- Feedback