From: Rick Jelliffe <ricko@allette.com.au>
Date: Wed Jun 30 2004 - 15:51:47 UTC

Appended is my working list of corrections.

Thanks especially to Daniel Cazzulino, who has kindly reviewed the draft
looking at
what would be needed to update his .NET implementation of Schematron 1.5 to
draft ISO form. (I have replied to him separately concerning some issue
that he
raised that I do not think require action.)

Ken or Bryan (or anyone): what are the duties of the editor at this stage?

The first table gives a couple of dozen typos etc, which do not change
anything substantial.
I believe that these are my perrogative to fix for the DIS (if that is
the next stage),
as normal editorial duties.

The second table reveals a couple of things where the definitions need
an extra
paragraph. Because these involve new text (a couple of sentences) though not
new sentences, do we have to get a national body to raise the points
officially?

The third table includes some wordsmithing. Do editor's have any
flexibility for
this, at this stage?

In other news, Dare Obasanjo, who is in charge of the XML APIs for Longhorn
at Microsoft has suggested that he may be interested in adding Schematron
to Longhorn's API. That would be great, but we shall see.

Also on my todo list at the moment is to prepare an HTML version of the
draft (by request from someone who will not read PDF) and to prepare
an unofficial DTD (for someone who cannot read RELAX NG).

Cheers
Rick Jelliffe

Schematron_Corrections

Corrections for CD of ISO Schematron

The following are the corrections known to be required for the Comittee Draft of ISO Schematron as at 2004-06-30

Editorial Corrections

These represent corrections due to editorial errors and not changes or adjustments to ISO Schematron. In the following, "G" means General and "T" means Technical following the ISO balloting categories; where General are typos, formatting errors, arrangement and incorrect language, and Technical includes most other things.

Number	From	Class	Issue	Cause	Proposed Solution
1	DC	G	RELAX NG production for ns contradicts s5.2.7: is attribute "prefix" optional?	Typo: prefix has never been optional	Remove "?" from schema for ns/@prefix
2	DC	G	RELAX NG production for "rule" contradicts s5.3.5: is attribute "flag" allowed on rules?	Editorial	Remove "or rule" from text of 5.3.5
3	DC	T	RELAX NG production for "assert" and "report" seem incomplete: is element "value-of" allowed as child of "assert" and "report"	Editorial: value-of was discussed in the WG earlier, and in the DTD for Schematron 1.6	Restore "value-off" in RELAX NG schema
4	DC	G	RELAX NG productions allow attribute "fpi" in more places than mentioned by s5.3.6	Editorial: infelicity	Append text "and so on" to definition in s5.3.6
5	DC	G	Spelling error "ancilliary"	Typo	Global replace "ancilliary" with "ancillary"
6	DC	G	Grammar error s6.2 "To simplifying"	Typo	Replace with "To simplify"
7	DC	G	s6.5 uses sch: prefix, unlike rest of document	Editorial: infelicity.	Remove all uses of sch: in text
8	DC	G	s 6.5 Reference to obsolete "key" element in last para	Editorial: infelicity. It belongs in the binding document	Move last paragraph of to the Query language binding, nd make sure it uses an "xslt" prefix for clarity
9	DC	G	s6.1 has word "performs" twice	Typo	Fix text
10	DC	T	s6.1 refers to "external variables"	Editorial: External variables were not included in this draft, though they were mentioned in WG.	Remove reference. (If national bodies want external variables, they are just another case of <let> variables and could be reintroduced trivially.)
11	DC	G	x4.2 use of "iff"	Editorial: infelicity	Replace with "if"
12	DC	T	"variable references in the string are resolved" introduces a query-language specific	Editorial: infelicity. We had decided to remove all query-language-specific features	use "in the select attribute" rather than "in the string"
14	DC	G	5.2.13 word "empty"	Editorial: typo	Remove "empty"
15	DC	T	5.2.5 let element says it returns a string, however this is query-language specific	Editorial: infelicity. We had decided to remove all query-language-specific features	Remove "that returns a string"
16	DC	G	s3.2.2 "possibly with other constraints ..." is extraneous	Editor: infelicity	Remove starting from "possibly"
17	DC	G	s5.3.9 Ambiguous: what path expression?	Editorial: infelicity	Append "of the subject attribute" to clarify
18	DC	G	Annex A is it "inclusion" or "inclusions"	Editorial: typo	Change the name used to "inclusions"
19	RJ	G	s3.1.16 definition is grammatically incorrect and is missing a "not"	Editorial: typo	Change "that has been" to "has not been"
20	DC	G	The RELAX NG schema contradicts the body text: is the attribute called "path" or "select"?	Editorial: typo	The attribute is "select"
21	RJ	G	In s 5.2.2 and s5.2.12, the terminology is incorrect	Editorial: typo	In the second sentence of each, replace "context" with "content".
22	RJ	G	S6.1 the word "notationally" does not exist	Editorial: typo	Replace "notationally" with "notionally"
23	DC	G	s5.2.5 the term "constant" is used, however it is "variable" in the definitions section	Editorial: typo	Replace "constant" with "variable" (twice)
24	DC	G	s5.2.14 word "either" is unexpected	Editorial: typo	Remove word "either"
25	DC	G	s4.2 "@default-phase" is used but in the RELAX NG schema it is @defaultPhase. Also s5.2. refers to "phase attribute" on the schema element.	Editorial:typo. It has always been defaultPhase	Correct both to defaultPhase
26	RJ	G	s5.3.12 is "is evaluated in the context of the the current subject node" correct?	Editorial: typo	Replace with "subject node" with "context node"
27	RJ	G	In the predicate logic, the initial upsde-down A (for all) is missing	Typesetting	Fix
28	RJ	G	In the notation section,the initial E (is element of) is missing	Typesetting	Fix
29	RJ	G	Can we use RELAX NG Compact Syntax?	Committee: will the TR or appendix be ready in time for use?	Assume yes. Clean up comments at start. Need reference. Clarify that it is compact syntax being used.
30	RJ	G	Case of "this spec" is sometimes wrong	Typesetting	Fix
31	RJ	G	Name and numbers of parts need updating	Editorial: infelicity	Fix
32	DC	?	S 4.2 second and third definitions are identical	(??? Check ???)	????

G = General
T = Technical

Missing Text

The following items are where the schema implies a behaviour, but it is not adequately explained in the text.

Number	From	Class	Issue	Cause	Proposed Solution
1	DC	T	s5.2.6 does not explain that an unspecified "select" attribute supplies the name of the curent context		Clarify
2	DC	T	"is-a" attribute is not mentioned in 5.2.9, neither is "abstract".		???
3	RJ	T	Double check that section using text in a vocabulary is good enoguh		???
4	RJ	G/T	s3.10 definition of subject is a little muddled	Editorial: infelicity	??? s3.10 add "typically". s4.2 replace "from context of subject y" with "from the context of y"

Wordsmithing

The following are suggestions for improved wording, without altering meaning.

Number	From	Class	Issue	Cause	Proposed Solution
1	DC	T	"A list of assertions tested within a context. The context attribute provides the rule context expression." better as "A list of assertions tested within the context specified by the required context attribute."		Change
2	DC	G	the spec should say pretty much up-front that an assertion is represented either as an assert or a report element. Otherwise, the reader may be confused into thinking we're talking about the former and not the later.		Change

Reviewers:

RJ = Rick Jelliffe (Editor)
DC = Daniel Cazzulino (Implementor)

--
DSDL members discussion list
To unsubscribe, please send a message with the
command  "unsubscribe" to dsdl-discuss-request@dsdl.org
(mailto:dsdl-discuss-request@dsdl.org?Subject=unsubscribe)

Received on Wed Jun 30 17:52:05 2004

This archive was generated by hypermail 2.1.8 : Fri Dec 03 2004 - 14:00:28 UTC

[dsdl-discuss] Current list of corrections for draft CD Schematron

Corrections for CD of ISO Schematron

Editorial Corrections

Missing Text

Wordsmithing