Level 4 Schema and Schematron Feedback - Revision history

Kshawkin: /* Tester: Sebastian Rahtz */ resolutions

2011-07-05T21:44:31Z

‎Tester: Sebastian Rahtz: resolutions

Kshawkin: /* Tester: Kevin Hawkins */ what to do about elementSpec rendering

2011-07-05T21:43:16Z

‎Tester: Kevin Hawkins: what to do about elementSpec rendering

Kshawkin: /* Tester: Michelle Dalmau */ responses to Michelle's things

2011-07-05T16:02:56Z

‎Tester: Michelle Dalmau: responses to Michelle's things

Kshawkin: /* Tester: Enter Your Name */ what Sebastian sent by email

2011-05-01T18:07:18Z

‎Tester: Enter Your Name: what Sebastian sent by email

Kshawkin: /* Tester: Kevin Hawkins */ now say to omit entire element defintion

2011-05-01T17:56:02Z

‎Tester: Kevin Hawkins: now say to omit entire element defintion

Kshawkin: /* Tester: Enter Your Name */ took this section and added note about use of elementSpec

2011-05-01T17:52:00Z

‎Tester: Enter Your Name: took this section and added note about use of elementSpec

Mdalmau: /* Tester: Michelle Dalmau */

2011-03-11T02:35:10Z

‎Tester: Michelle Dalmau

Mdalmau: /* Tester: Michelle Dalmau */

2011-03-11T02:33:42Z

‎Tester: Michelle Dalmau

Mdalmau: /* Tester: Michelle Dalmau */

2011-03-11T02:30:48Z

‎Tester: Michelle Dalmau

Mdalmau: /* Tester: Michelle Dalmau */

2011-03-11T02:23:52Z

‎Tester: Michelle Dalmau

← Older revision		Revision as of 21:44, 5 July 2011
Line 76:		Line 76:
	</pre>		</pre>
	</blockquote>		</blockquote>
		+
		+	: Resolved ([[User:Kshawkin\|Kshawkin]] 17:44, 5 July 2011 (EDT))

← Older revision		Revision as of 21:43, 5 July 2011
Line 46:		Line 46:

	* 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.		* 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.
		+	: Later, Syd will change XSLT so that it omits exemplum elements from output. Some day in the future, we will figure out a mechanism that allows us to supply our own examples not in P5 for use of particular elemens. The output will include only our examples and none of those in P5. ([[User:Kshawkin\|Kshawkin]] 10:05, 5 July 2011 (EDT))

	==Tester: Sebastian Rahtz==		==Tester: Sebastian Rahtz==

@@ Line 6: / Line 6: @@
 * 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.
+:: Has been fixed. ([[User:Kshawkin|Kshawkin]] 12:02, 5 July 2011 (EDT))
 * 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.
 ** <div type="half_title" rend="center"> 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.
 * 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: <div type="preface">: 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==

@@ Line 26: / Line 26: @@
 * 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: Sebastian Rahtz==
-* List feedback, problems encountered, etc. in bulleted list form.  Provide detailed examples please so that we may make corrections more easily.
-* Feedback
+From an email from Sebastian:
-* Feedback

@@ Line 24: / Line 24: @@
 ==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 examples from the ODD since creating valid examples for each element is a huge amount of work which makes maintenance of the BP that much harder.
+* 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==