Re: vCard confusion and RDF insufficiency

On 26.07.2007 10:04:46, Garret Wilson wrote:
>* Benjamin: "Yes, that's a general suggestion, which usually coves both 
>collections and containers, as they introduce intermediate nodes." 
>(semantic-web@w3.org 2007-07-26)
please, don't cite me out of context. *If* you don't need ordering,
stay away from unnecessarily complex constructs. You asked for a
way to model sorted lists. rdf:Seq is one you could use.

>* For rdf:Seq, you can have multiple rdf:_3 properties, for example.
If you don't model your props as IFPs, that's not very likely to 
happen accidentally. And from a practical POV, at least you can merge
the data and do some sorting.

>* For rdf:Seq, you could have a rdf:_2809 property with no other 
>properties, for example.
again, as the MF folks would say: where is the real-world data
where this happens and where that really causes an app to break.

>* There is no way to specify the end of an rdf:Seq list.
Is that required for the use cases at hand?

>It seems fundamentally wrong to me to allow a particular serialization 
>format of a general model to dictate the construction of an ontology.
Noone forces you to use RDF. Maybe that's the whole issue here. You
say you want to use RDF, but actually you don't. Or you can't. But
then it won't help to repeat your rant a dozen times. A standard RDBMS
won't allow you to use single-column lists, although they might look
like a beautiful feature for many use cases. Shouting "Codd sucks" all
day long won't really bring you forward. And as Sandro mentioned already,
feel free to propose RDF 2.0, but that's probably not the best approach
to getting that rdf/vcard spec done this decade ;)


Benjamin

--
Benjamin Nowack
http://bnode.org/

Received on Thursday, 26 July 2007 17:48:09 UTC