- From: Seaborne, Andy <andy.seaborne@hp.com>
- Date: Wed, 27 May 2009 08:52:35 +0000
- To: Axel Polleres <axel.polleres@deri.org>
- CC: Boris Motik <boris.motik@comlab.ox.ac.uk>, 'Alan Ruttenberg' <alanruttenberg@gmail.com>, "eric@w3.org" <eric@w3.org>, "sandro@w3.org" <sandro@w3.org>, "public-rdf-text@w3.org" <public-rdf-text@w3.org>
> -----Original Message----- > From: Axel Polleres [mailto:axel.polleres@deri.org] > Sent: 26 May 2009 19:50 > To: Axel Polleres > Cc: Seaborne, Andy; Boris Motik; 'Alan Ruttenberg'; eric@w3.org; > sandro@w3.org; public-rdf-text@w3.org > Subject: regrets and last input for the call... > > As I can't join the call, here some last input for word-smithing... > > At a second read... what I just committed reads strange: > > >> Maybe (intro): """ ...typed rdf:text literals MUST NOT occur in > >> published RDF content or in the results of SPARQL basic graph > pattern > >> matching [SPARQL] using extended SPARQL Basic Graph Matching""" > > I won't object against it, but how about rather: > > "In order to prevent interoperability problems between RDF processors > that support rdf:text and those that do not, typed rdf:text literals in > published RDF content MUST NOT be generated by RDF processors, such as > APIs, or SPARQL engines that implement SPARQL basic graph pattern > matching [SPARQL] using extended SPARQL Basic Graph Matching;" I don't think this adds anything, and it opens up discussion of APIs which to my mind are not to do with specs of information exchange across the web. It is not clear what it says about writing RDF/XML and putting it on a web server, or things that generate RDF but do not consider themselves "RDF processors". Andy
Received on Wednesday, 27 May 2009 08:53:52 UTC