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

RE: UPDATED: Pointers changes and issues

From: Carlos Iglesias <carlos.iglesias@fundacionctic.org>
Date: Wed, 18 Jul 2007 13:15:58 +0200
Message-ID: <09700B613C4DD84FA9F2FEA521882819023BDEB9@ayalga.fundacionctic.org>
To: "Johannes Koch" <johannes.koch@fit.fraunhofer.de>, <public-wai-ert@w3.org>


Hi Johannes,

> > 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?


Only ptr:offset and the inherited ptr:reference, so the distinction would come from the context (the scope within which the pointer operates)


> > 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?


I don't see your point here.
If we use the classes instead of the Literals we'll basically have the same as now but using classes instead Literals.
If we merge both into a single OffsetPointer we'll have a pointer to the start (as in the RangePointer) and a value (a class or a Literal) with a number of characters or bytes from the start, which is different from having a pointer to the start and a pointer to the end (in spite of being similar) 

Is there anything I'm missing?
 

> 2.4.4 ByteSnippetRangePointer Class
> Is ptr:byteSnippet Base64 encoded?


I think it should. No decision made until now.

Regards,
 CI.
 
--------------------------------------

Carlos Iglesias

CTIC Foundation
Science and Technology Park of Gijón
33203 - Gijón, Asturias, Spain 

phone: +34 984291212
fax: +34 984390612
email: carlos.iglesias@fundacionctic.org
URL: http://www.fundacionctic.org
Received on Wednesday, 18 July 2007 11:15:40 GMT

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