W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > April to June 2007

Re: Attributes in the results format

From: Steve Harris <steve.harris@garlik.com>
Date: Mon, 30 Apr 2007 18:13:17 +0100
Message-Id: <331BA08E-706D-4E8C-8F05-D098AD196FB2@garlik.com>
Cc: RDF Data Access Working Group <public-rdf-dawg@w3.org>
To: andy.seaborne@hp.com

On 30 Apr 2007, at 15:06, Seaborne, Andy wrote:
...
> 1/ Keep the status quo.  Nothing for REDUCED, weak text for  
> definitions.
>
> 2/ Make the attributes only be true when explicitly requested.
>    2a/ No reduced="true"
>    2b/ Add a reduced=
>
> 3/ Drop one or both of the current attributes.  Fix or leave the  
> other.
>
> I think the intention was to use attributes to specificy whether an  
> explciit distinct or ordered request was made (by including the  
> keywords or vai an API), not to make the query processor determine  
> the fact for the client in query requests without some explicit  
> marker.  That is the "such as" means this is "one way of doing it  
> but alternative indications, like API calls are OK".
>
>
> I am against (1) and for (3), dropping both attributes.

I'm in favour of (3) dropping both - I haven't seen any benefit to  
them other than enabling more elaborate pretty-printing of results.

- Steve

-- 
Steve Harris
Garlik Limited
Gainsborough House
2 Sheen Road
Richmond  TW9 1AE

T   +44(0)20 8973 2465
F   +44(0)20 8973 2301
www.garlik.com

Registered in England and Wales 535 7233 VAT # 849 0517 11
Registered office: 42-46 High Street, Esher, Surrey KT10 9QY
Received on Monday, 30 April 2007 17:13:35 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:36 GMT