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

Re: construct starting to feel like a separate interface

From: Dan Connolly <connolly@w3.org>
Date: Mon, 09 May 2005 10:27:00 -0500
To: kendall@monkeyfist.com
Cc: DAWG Mailing List <public-rdf-dawg@w3.org>
Message-Id: <1115652420.28180.378.camel@localhost>

On Mon, 2005-05-09 at 11:03 -0400, Kendall Clark wrote:
> On Mon, May 09, 2005 at 10:31:46AM -0400, Kendall Clark wrote:
> 
> > I believe that by moving CONSTRUCT to a separate interface (well, I
> > would move it into two separate interfaces: SparqlConstruct and
> > SparqlConstructX), the "query-result" type would become:
> > 
> >     <xs:element name="query-result">
> >         <xs:element ref="xrf:sparql"></xs:element>
> >     </xs:element>
> 
> D'oh! I forgot about DESCRIBE -- pesky DESCRIBE.
> 
> Hmm, I think, then, that DESCRIBE and CONSTRUCT stand or fall
> together, so I'm leaning toward something like this:
> 
> SparqlQuery (SELECT & ASK)
> SparqlGraph (CONSTRUCT & DESCRIBE)

Yes, that seems right... I hope to verify my intuitions
with code later today or tomorrow.

I haven't thought about the others as much...

> SparqlQueryX 
> SparqlGraphX
> SparqlMaintain
> SparqlService
>
> Interfaces increase further (at least two, at most five more) if we
> include the (orthogonal, IMO) XSLT transformation stuff.
> 
> Kendall Clark
-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E
Received on Monday, 9 May 2005 15:27:30 GMT

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