- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Wed, 10 Jul 2013 16:25:32 +0200
- To: "'Pat Hayes'" <phayes@ihmc.us>
- Cc: "'Linked JSON'" <public-linked-json@w3.org>, "'RDF WG'" <public-rdf-wg@w3.org>, "'public-openannotation'" <public-openannotation@w3.org>
On Wednesday, July 10, 2013 5:23 AM, Pat Hayes wrote: > On Jul 9, 2013, at 4:23 AM, Markus Lanthaler wrote:> > > On Tuesday, July 09, 2013 6:46 AM, Pat Hayes wrote: > >> On Jul 8, 2013, at 1:01 PM, Robert Sanderson wrote: > >>> Something like: > >>> > >>> rdf:listHead -- The object, which must be a blank node with > rdf:type > >> rdf:List, is the first entry in a list associated with the subject > >> resource. > >> > >> I guess I don't follow this. If the object is of type LIst, and it > is > >> the first item in a list, then you have a list of lists. Which is > >> legal, but I don't see how it helps with the problem we have here. > And > >> what does "associated with" mean? > > > > I think was Robert meant was something like > > > > <> rdf:ListHead _:head . > > <> ... other properties of <> ... > > _:head rdf:type rdf:List . > > _:head rdf:first ... > > _:head rdf:rest _:item2 . > > _:item2 ... > > Ah, OK. But then we get back to my previous point. All this wriggling > can't get us past the fact that if this means what it is supposed to > mean, then the truth conditions on rdf:ListHead are going to be that > > <1> rdf:ListHead <2> is true just when <1> = <2>. Fully agree but I think what Robert is looking for is something similar to rdf:value but specifically for lists. -- Markus Lanthaler @markuslanthaler
Received on Wednesday, 10 July 2013 14:26:11 UTC