- From: Michael A Squillace <masquill@us.ibm.com>
- Date: Wed, 14 Jan 2009 12:16:37 -0500
- To: public-wai-ert@w3.org
- Message-ID: <OFE363634D.84C5F6C4-ON8525753E.005EC076-8625753E.005EEBD3@us.ibm.com>
Group: Attached please find my edits and suggestions for the most recent Pointers in RDF document at: http://www.fundacionctic.org/uaw/ERT-WG/2009/EARL_draft.html Some chief edits and questions: Note: For all of these major edits, the original remains in comments prior to the edit. My suggestions begin with '<!-- MAS -->'. Minor edits (e.g. spelling, typographical) are not noted. 1. rewrote use cases section; still think we could use one or two other use cases 2. rewrote description of Pointer class; spec says this could be used directly but calls it abstract. I suggest leaving it as abstract and requiring the use of subclasses either in the specification or created elsewhere in other vocabularies. Also, with this approach, there should be a Related Classes section (see PointersGroup class, for example) that points to subclasses in this spec. If we want to permit direct use of the Pointer class, then an example should be provided. 3. rewrote descriptions of RelatedPointers and EquivalentPointers classes 4. didn't modify it, but recommend that the description for SinglePointer look much like that for Pointer class; make it abstract and require the use of more specific subclasses 5. in the example for CharSnipetRangePointer, we refer to cnt:chars. Does this mean that processors of Pointers in RDF must also know how to process Representing Content in RDF? (May have already discussed this but couldn't find anything in minutes.) 6. Is a pointer property along with a Pointer class going to be confusing? Is there another name for the property (e.g. memberPointer)? 7. starting with Section 3 Properties, the 'in domain of' and 'in range of' lists refer to earl:xxx QNames; should these be ptr:xxx QNames? 8. rewrote abstract but still needs work I did not review the apendicies, although quick glance shows them acceptable for a first draft. (See attached file: EARL_draft-mas.html) --> Mike Squillace IBM Human Ability and Accessibility Center Accessibility Tools Framework (ACTF) co-technical lead http://www.eclipse.org/actf W:512.286.8694 M:512.970.0066 External: http://www.ibm.com/able Internal: http://w3.ibm.com/able
Attachments
- text/html attachment: EARL_draft-mas.html
Received on Wednesday, 14 January 2009 17:17:29 UTC