W3C home > Mailing lists > Public > public-wai-ert@w3.org > July 2007

Re: UPDATED: Pointers changes and issues

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Wed, 18 Jul 2007 14:47:24 +0200
Message-ID: <469E0BDC.1020903@w3.org>
To: Carlos Iglesias <carlos.iglesias@fundacionctic.org>
CC: public-wai-ert@w3.org

Hi Carlos,

Thanks for updating this document, please find some comments below (some 
of them are similar to or repeat those from Johannes):

COMMENT 1:
Issue #1: I propose we adopt dc:hasVersion rather than ptr:version

COMMENT 2:
Issue #6 & #8: I don't think we should merge the two classes, though it 
may be interesting to have a parent "OffsetPointer" class with a 
ptr:offset property that is then used differently in the CharOffset or 
the ByteOffset classes

COMMENT 3:
Issue #9: I don't think I understand the problem, my understanding so 
far was that a CSS Selector is something like "h2" or "#id" etc.

COMMENT 4:
Issue #11: if we don't drop this pointer (at least for now), then we 
will need to publish a definition (and algorithm) of what we mean by 
"HTML Pointer" (possibly in a separate document?). We would also need 
dc:hasVersion to refer to the version of the pointer definition (we 
shouldn't worry about HTML5 yet)

COMMENT 5:
2.4 CompoundPointer: should ptr_startPointer and ptr:endPointer be 
ptr:Pointer rather than ptr:SinglePointer?

COMMENT 6:
2.4 CompoundPointer: do we need 2.4.3 CharOffsetRangePointer and 2.4.5 
ByteOffsetRangePointer? I think using CharOffset and ByteOffset as start 
and end pointers in a RangePointer should suffice, no?

COMMENT 7:
2.4 CompoundPointer: how about we have a simple SnippetPointer that can 
be used with the RangePointer to replace 2.4.2 CharSnippetRangePointer 
and 2.4.4 ByteSnippetRangePointer (as in the comment above)?

COMMENT 8:
All offsets should use integer values rather than Literal.

COMMENT 9:
Putting it all together and rearranging some, I came up with the 
following model for discussion:

Pointer (ptr:reference)
|-PointerGroup (ptr:pointer)
| |-RelatedPointer
| '-EquivalentPointer
|-SinglePointer (dc:hasVersion, ptr:expression)
| |-XPathPointer (ptr:namespace)
| |-XPointerPointer (ptr:namespace?)
| |-[HTMLPointer]
| '-CSSPointer
|-OffsetPointer (ptr:offset)
| |-CharOffsetPointer
| '-ByteOffsetPointer
|-SnippetPointer (ptr:snippet)
| |-CharSnippetPointer
| '-ByteSnippetPointer
|-CompoundPointer (ptr:startPointer)
| |-StartEndPointer (ptr:endPointer)
| '-StartOffsetPointer (ptr:offsetPointer)
'-LineCharPointer (ptr:line, ptr:char)


Regards,
   Shadi


-- 
Shadi Abou-Zahra     Web Accessibility Specialist for Europe |
Chair & Staff Contact for the Evaluation and Repair Tools WG |
World Wide Web Consortium (W3C)           http://www.w3.org/ |
Web Accessibility Initiative (WAI),   http://www.w3.org/WAI/ |
WAI-TIES Project,                http://www.w3.org/WAI/TIES/ |
Evaluation and Repair Tools WG,    http://www.w3.org/WAI/ER/ |
2004, Route des Lucioles - 06560,  Sophia-Antipolis - France |
Voice: +33(0)4 92 38 50 64          Fax: +33(0)4 92 38 78 22 |
Received on Wednesday, 18 July 2007 12:50:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:28 GMT