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

Re: UPDATED: Pointers changes and issues

From: Johannes Koch <johannes.koch@fit.fraunhofer.de>
Date: Wed, 18 Jul 2007 11:58:18 +0200
Message-ID: <469DE43A.1040602@fit.fraunhofer.de>
To: public-wai-ert@w3.org

Carlos Iglesias schrieb:

> 2.3.4 CharOffsetPointer Class
[...]
> ISSUE #6: We can think about merging this one and the following ByteOffsetPointer Class into a single OffsetPointer Class.
> 
> ptr:CharOffsetPointer (rdfs:subClassOf ptr:SinglePointer)
>     // number of characters from the start of the reference
>     ptr:charOffset (rdfs:range rdf:Literal)

Which property/properties would the OffsetPointer have? If it's only a 
ptr:offset property, how to distinguish between a character or byte offset?


> 2.3.7 HTMLPointer Class
[...]
> We need to advance in one of the following directions:
[...]
>     * Throw the idea completely out of the document.

For now I prefer this "solution" :-)


> 2.4.3 CharOffsetRangePointer Class
[...]
> ISSUE #13: We can think about replacing the Literal value with a CharOffsetPointer single Pointer (or a new generic OffsetPointer as seen at issues #6 and #8)
[...]
> 2.4.5 ByteOffsetRangePointer Class
[...]
> ISSUE: #15: We can think about replacing the Literal value with a ByteOffsetPointer single Pointer (or a new generic OffsetPointer as seen at issues #6 and #8)

Wouldn't that make the CharOffsetRangePointer and ByteOffsetRangePointer 
equal to the RangePointer?


2.4.4 ByteSnippetRangePointer Class
Is ptr:byteSnippet Base64 encoded?
-- 
Johannes Koch
BIKA Web Compliance Center - Fraunhofer FIT
Schloss Birlinghoven, D-53757 Sankt Augustin, Germany
Phone: +49-2241-142628    Fax: +49-2241-142065
Received on Wednesday, 18 July 2007 09:58:53 GMT

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