Thanks for the comments on my draft for Part 7. I am improving
it now.
> 1) How will CVDL be invoked? In the introduction it says "Descriptions
> in this language may be referenced from schemas". What schema languages
> provide means of referencing character sets? How do they do this?
To invoke CRDL from RNG, we have to introduce an attribute to
<text>. This attribute also has to be added to the compact
syntax.
I guess that Schematron can invoke CRDL without revising 19757-3,
but I am not sure.
> The
> introduction also states "Furthermore, they may also be referenced from
> forms and stylesheets." How do you reference a character set from a form
> (e.g. an XForm) or a CSS stylesheet?
Again, XForms and CSS have to be extended.
> 2) Should clause 6 refer to the whole of the W3C Schema regular
> expression language, or just to subclause F.1, which defines how
> character classes are defined? What is the relationship between the
> "Unicode regular expressions" referred to in clause 6 and XML Schema
> character classes?
The whole of the W3C Schema regular expression language, since
each defaulat grapheme cluster is represented by
a sequence of Unicde code points.
> 3) What the relationship between graphemes and grapheme clusters? For
> example, how can you say that a character set may not include an e acute
> character or an e with a combining acute, but may have other letters
> combined with the combining acute code?
They are defined in Unicode Standard Annex #29 Text Boundaries.
I will add this as a normative reference.
http://www.unicode.org/reports/tr29/
> 4) The definition of hull in Clause 5 is somewhat circular: it reads "A
> hull gives an outer boundary so that characters or grapheme clusters
> which are not in the hull are guaranteed not to be in the collection;"
> We suggest that "not in the hull" be changed to "not defined within the
> specified range". This would also require a change to the definition of
> hull in 3.3. We think that it may be necessary to state explicitly that
> a hull is a single range of characters, rather than a "set of characters
> and grapheme characters". If a hull can be defined using any XML Schema
> regular expression it could be defined as a set of single characters
> plus a set of ranges of characters. Is this really what you had in mind
> for a "hull"?
No. A kernel is a set of characters and default grapheme
clusters and a hull is also such a set.
I will improve the text, but Unicode Standard Annex #29 probably
addresses most of the questions.
> 5) Need to clarify both notes at the end of clause 6: in the first one
> there is the word See on its own at the end of the note, without a
> qualifying reference; in the second it is unclear how a single LF could
> ever match a Unicode expression. Please simplify these notes.
Accept.
> 6) The reference to "RELAX NG schema in the compact syntax" at the start
> of clause 7 should be replaced by a formal reference to the amendment
> for Part 2.
Accept.
> 7) The grammar of the first para of 8.7 needs adjusting. It probably
> should read: "IANA charsets and other implementation-dependent encodings
> are named collections. The semantics are implementation dependent." How
> are "implementation-dependent encodings" assigned names?
For example, Java has lots of encoding names, some of which are
not registered at IANA. Such encoding names are
implementation dependent, and we cannot say anything about them
in this standard.
> 8) What is meant by the term "decomposition" in the second paragraph of
> clause 9. Is decomposition defined within the Unicode specification? If
> so this should be explicitly stated.
See Unicode Standard Annex #29.
> 9) In clause 6 the phrase "strings u and v matches e" should be adjusted
> to "strings u and v match e".
Done.
> 10) In clause 8.2, Case 3, change both occurrences of "has" to "have"
Done.
> 11) Ensure consistency of use of periods after entry in lists. Sometimes
> you have them on all items, sometimes on only the last entry in the
> list. The use of periods should be consistent.
Accept.
> 12) In the last para of clause 9 please change "but rather examine the
> string directly" to "but rather examines the string directly."
Done.
> 13) An example instance would make it much easier to understand the
> specification.
Accept.
-- MURATA Makoto <murata@hokkaido.email.ne.jp> -- 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 Sat Aug 12 03:16:15 2006
This archive was generated by hypermail 2.1.8 : Sat Aug 12 2006 - 06:23:03 UTC