Difference between revisions of "Level 4 Schema and Schematron Feedback"
Jump to navigation
Jump to search
(→Tester: Enter Your Name: took this section and added note about use of elementSpec) |
(→Tester: Kevin Hawkins: now say to omit entire element defintion) |
||
Line 24: | Line 24: | ||
==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. I recommend omitting all | + | * 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 resolver. I recommend omitting all element definitions since creation and maintenance of these is too much for us to undertake. |
==Tester: Enter Your Name== | ==Tester: Enter Your Name== |
Revision as of 19:56, 1 May 2011
>>Return to testing instructions: Feedback_on_the_Best_Practices_for_TEI_in_Libraries_ODD_Documentation_and_Schemas
Tester: Michelle Dalmau
Comments/Feedback
- 1001 errors generated!
- Some are due to non-compliance for one reason or another (usually trivial oversights or value requirements). For example:
- <tagUsage gi="div">No numbered divs used.</tagUsage> should have a value of either: "Numbered divs used." or "Unnumbered divs used."
- element "editorialDecl" incomplete; missing required element "p" but I have a paragraph in there so I don't know what this error message means
- Description: element "back" incomplete; expected element "div" or "div1". Well I don't have back matter, but an empty <back/> tag caused the error.
- Most complaining about an encoding practice either too stringently or not supported by the schema
- Description: element "particDesc" not allowed anywhere; expected the element end-tag or element "langUsage" or "textClass". This error perplexes me. The particDesc appears where it should in the Header. It appears after langUsage and right before textClass. Even if prosopography can be considered a level 5 activity, should it choke on level 4?
- Many errors generated as the result of the prosopography with <listPerson> <person> etc.
- Many, many @corresp errors that reference the people in the prosopography.
- element "pb" not allowed here; expected the element end-tag or element "div". In this case, my <pb> was inside the <front> tag. It shouldn't complain.
- in the front matter is not supported ??? Description: attribute "type" (and "rend") not allowed here; expected attribute "n", "xml:id", "xml:lang" or "xml:space". Why not? And why can't we apply @rend to any chunk of markup?
- Can't have a <bibl> in my half_title div either: Description: element "bibl" not allowed here; expected the element end-tag or element "div", "figure", "gap", "head", "lb", "note", "opener" or "pb". Not sure why not.
- Description: element "particDesc" not allowed anywhere; expected the element end-tag or element "langUsage" or "textClass". This error perplexes me. The particDesc appears where it should in the Header. It appears after langUsage and right before textClass. Even if prosopography can be considered a level 5 activity, should it choke on level 4?
- Crazy errors
- Error messages don't line up with the highlighting in the XML (or anywhere near it). Probably because of all the many errors so I'll try and isolate after I work through the rest of the messages.
- Can't seem to type any of my divs. That's crazy: : Description: attribute "type" not allowed here; expected attribute "n", "xml:id", "xml:lang" or "xml:space". Those attributes seem to correspond with <pb> so I moved the surrounding <pb> inside and outside the div but the error message didn't change.
- Description: element "fw" not allowed anywhere. FormeWorks occur after the page break tag. Why not?
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 resolver. I recommend omitting all element definitions since creation and maintenance of these is too much for us to undertake.
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