Re: UPDATED: Pointers changes and issues

Carlos Iglesias schrieb:
> 
> 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)

Could you please elaborate?

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

What is the difference then between
ptr:CharOffsetRangePointer
|- ptr:charOffset (rdfs:range ptr:ByteOffsetPointer)

and

ptr:RangePointer
|- ptr:endPointer (rdfs:range ptr:SinglePointer)

? Both are pointing to the end of the range.

If you want to _point_ to the end of the range, you can use a
RangePointer. I though the intention of the
CharOffsetRangePointerByteSnippetRangePointer was to specify the
_length_ of the range.

-- 
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 11:49:49 UTC