- From: <editor@content-wire.com>
- Date: Fri, 25 Jan 2008 18:08:25 +0700
- To: "Dan Brickley" <danbri@danbri.org>
- Cc: <semantic-web@w3c.org>, "Ralph Swick" <swick@w3.org>
Thats the feedback from an outsider (alien from other planet) I think what I call operators seem to correspond to keywords in the new document But such keywords as listed in the new spec seem to have some new types I ll just take it 'as is' for the moment, will investigate later, thanks pdm NEW Keywords: BASE SELECT ORDER BY FROM GRAPH STR isURI PREFIX CONSTRUCT LIMIT FROM NAMED OPTIONAL LANG isIRI DESCRIBE OFFSET WHERE UNION LANGMATCHES isLITERAL ASK DISTINCT FILTER DATATYPE REGEX REDUCED a BOUND true sameTERM false OLD * PREFIX — specification of a name for a URI (like RDQL’s USING). * SELECT — returns all or some of the variables bound in the WHERE clause. * CONSTRUCT — returns a RDF graph with all or some of the variable bindings. * DESCRIBE — returns a description of the resources found. * ASK — returns whether a query pattern matches or not. * WHERE — list, i.e. conjunction, of query (triple or graph) patterns. * OPTIONAL — list, i.e. conjunction, of optional (triple or graph) patterns. * AND — boolean expression (the filter to be applied to the result).[1] -------------------------------------------------------------------------------- [1] Bailey. See 36. ----- Original Message ----- From: "Dan Brickley" <danbri@danbri.org> To: <editor@content-wire.com> Cc: <semantic-web@w3c.org>; "Ralph Swick" <swick@w3.org> Sent: Friday, January 25, 2008 5:30 PM Subject: Re: trivial question about SPARQL > > editor@content-wire.com wrote: >> thanks a lot Andy, Dan >> >> I think I am looking at too many documents at once at any given time >> had not seen the link to the new version, I knew it had to be somewhere >> >> I am finding it really difficult to find the uptodate docs on the site, >> is there a way of flagging the >> outdated stuff more prominently (put them in a liked category >> superseded_by comes to mind) or somethign > > The issue there is that W3C really doesn't like to change the bytes in the > file once published in /TR/ ... and so updating the document with status > information is tricky. > > I remember Ralph (cc:'d) once made a clever experiment that pulled in an > image (I think) indicating current status. But this didn't get adopted as > far as I know. Perhaps something similar could be done with an iframe or > unobtrusive Javascript, if it passed accessibility review. > > Good to have that feedback though... > > cheers > > Dan >
Received on Friday, 25 January 2008 11:01:22 UTC