Some ITS test results

Hi Yves, all,

A late Happy New Year, and some results of ITS testing:

-
http://www.w3.org/International/its/tests/expected/EX-locNoteRef-attribute-1-result.xml
seems to be incorrect: there is a <locNoteReference> in the ouput for
the its:locNoteRule element, although that element is not selected by
the rules element.
See
<o:node path="/myRes/head[1]/its:rules[1]/its:locNoteRule[1]"
outputType="new-value-local">
      <o:output o:locNoteType="description">
<o:locNoteReference>ErrorsInfo.html/#NotFound</o:locNoteReference>

      </o:output>
    </o:node>
and in
http://www.w3.org/International/its/tests/inputdata/EX-locNoteRef-attribute-1.xml
<its:locNoteRule locNoteType="description"
selector="//msg[@id='NotFound']" locNoteRef="ErrorsInfo.html/#NotFound"/>
the reason might be that the locNoteRef attribute is maybe interpreted
as local ITS markup?

-
http://www.w3.org/International/its/tests/expected/EX-locNoteRefPointer-attribute-1-result.xml
looks like as if there was s.t. like the following rules element:
<its:locNoteRule locNoteType="description" selector="//data[parent::string]"
    locNoteRefPointer="../@noteFile" />
howevever, there is a rules element with selector="//data", which
selects *all* <data> elements (not only the ones within <string> elements)

- A general comment on all "ref" attributes, e.g.
EX-locNoteRefPointer-attribute-1-result.xml  : We should make clear in
the tagset draft that a processor must be able to recognize "this is an
URI reference" (although there is no need to resolve the reference).
I.e., the processor must be able to produce <o:locNoteReference> instead
of <o:locNoteText>. This is especially an issue with a generalized
implementation which does not "know" about data category specific
information.

Cheers,

Felix

Received on Monday, 8 January 2007 00:50:36 UTC