W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > July to September 2004

Proposed reply to Chris Wilper: Real-world use case for 3.10

From: Tom Adams <tom@tucanatech.com>
Date: Mon, 26 Jul 2004 21:13:28 -0400
Message-Id: <2AE9EC5B-DF6A-11D8-982F-000A95C9112A@tucanatech.com>
To: public-rdf-dawg@w3.org

Below is an outline of my proposed reply to Chris Wilper on his use 
case for requirement 3.10, posted to public-rdf-dawg-comments@w3.org.


Hi Chris,

Thanks for your posting to the DAWG comments list. The DAWG is always 
happy to receive comments and use cases on its proposed requirements.

The requirement you noted was moved from PENDING to APPROVED at the 
DAWG face to face on the 15th July. You can view the details at:


Keep the comments coming!


On 06/07/2004, at 1:25 PM, Chris Wilper wrote:

> Hi,
> Looking at the Requirements/Use Cases document, I noticed that 3.10 
> and 3.10a
> had "Pending" status.  We[1] plan on using an rdf triplestore to back 
> a large
> metadata repository, exposed to other systems via the OAI-PMH[2].  
> While not
> being too domain and protocol-specific here, I'll describe our case:
> We have a large collection of metadata in a triplestore that we want to
> make available to people through a set of queries.  Someone typically 
> asks,
> "Give me the metadata that has changed since last week and is in XYZ
> collection", or simply, "Give me all the metadata".
> It is a requirement for us that the responses can come in chunks: XML 
> is
> sent over the wire, and rather than require all of our clients (and our
> server)
> to be able to handle arbitrarily large chunks of xml in one stream, our
> server
> can be configured to give only, say 1,000 responses, along with a
> "resumption token" that can be used for subsequent requests.
> Without the ability to specify LIMITS/OFFSETS with the triplestore 
> query, we
> would
> need to stream everything to disk and manage much more state within our
> application.
> [1] http://www.fedora.info/ and http://www.nsdl.org/
> [2] OAI-PMH is a protocol for exposing xml metadata in a repository.
>     See http://www.openarchives.org/OAI/openarchivesprotocol.html
> ___________________________________________
> Chris Wilper
> Cornell Digital Library Research Group
> http://www.cs.cornell.edu/~cwilper/
Tom Adams                  | Tucana Technologies, Inc.
Support Engineer           |   Office: +1 703 871 5312
tom@tucanatech.com         |     Cell: +1 571 594 0847
http://www.tucanatech.com  |      Fax: +1 877 290 6687
Received on Monday, 26 July 2004 21:13:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:00:44 UTC