W3C home > Mailing lists > Public > public-openannotation@w3.org > January 2013

Re: New Draft comments: Multiplicity

From: Antoine Isaac <aisaac@few.vu.nl>
Date: Tue, 29 Jan 2013 22:32:41 +0100
Message-ID: <51083FF9.1070500@few.vu.nl>
To: public-openannotation <public-openannotation@w3.org>
On 1/29/13 10:26 PM, Robert Sanderson wrote:
> On Tue, Jan 29, 2013 at 1:46 PM, Antoine Isaac<aisaac@few.vu.nl>  wrote:
>
>>>>>>>> 2. Mapping with RDF container classes.
>>>>>
>>>>> I guess that I'm hesitant to promote Bag and Alt.
>>>> Yes, and I think the best way not to forget about it is to note the
>>>> subclass mapping :-)
>>>
>>> In the description we now talk about "equivalent classes",
>>
>> Note: as you put it below, Alt and Bag should not be equivalent classes to
>> Choice and Composite.
>
> Yes, not in the OWL sense.
>
>
>>>> I'd argue that mentioning the axioms is useful even if the data producers
>>>> are the ones in charge of applying them...
>>> Could you write up a paragraph or so for them? Agreed that it would be
>>> good to be clear, and I'm not sure that I would do them justice.
>>
>> Editor's note: an algorithm to automatically derive oa:item statements from
>
> If we can get this finalized, I would like it to be just part of the
> specification rather than an editor's note.  I think it's valuable to
> explain.
>
>> the rdf:first/rdf:list pattern could be:
>>   1. Create a statement [l oa:item i .] for every statement [l rdf:first i .]
>
> Shouldn't there ever only be one rdf:first per rdf:List?


Yeah, but there are several lists (each one having an rdf:first).


>
>>   2. Create a statement [l oa:item i .] for every chain of statements [l
>> rdf:rest r . r oa:item i .] until no new statement can be created.
>
> Doesn't this imply that rdf:nil is also an oa:item of the List?  Can
> we avoid that?
>


I think it doesn't imply that. rdf:nil should appear as the rdf:rest of the "last list".

To rephrase it: the first axiom turns every rdf:first of the (nested) rdf:Lists into an oa:item; the second propagates every oa:item attached to a nested rdf:List into the "embedding" list--one step up the hierarchy of nested lists, until you reach the very first list, which is the body or the target or the selector.

Antoine
Received on Tuesday, 29 January 2013 21:33:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 29 January 2013 21:33:10 GMT