Re: Initial draft for the GRDDL Scenario gallery (editor's draft mechanics)

Below is an overview for the XForms usecase for the gallery

Use case #3 - A GRDDL Profile for XForms-based Webapps: Tom wants to extract transport semantics from an online form used to edit blog entries.

Tom has developed a weblog engine that utilizes <a 
href="http://www.w3.org/TR/xforms/">XForms</a> for editing entries 
remotely using the Atom Publishing Protocol.  Tom has found the use of 
XForms for authoring fragments of Atom quite useful for a variety of 
reasons.  In particular, the Atom Publishing Protocol's use of HTTP and <a 
href="http://en.wikipedia.org/wiki/Plain_Old_XML">POX</a> (Plain Old XML) 
as the primary remote messaging mechanism allows Tom to easily author 
various XForm documents that use XForm <a 
href="http://www.w3.org/TR/xforms/slice3.html#structure-model-submission">submission</a> 
elements to dispatch operations on web resources.

As a result, the XForms for dispatching these operations each contain a 
rather rich set of information about transport-level services in the form 
of service URLs, media-types and HTTP methods.  These are completely 
encapsulated in an XForms submission element.  It so happens that there is 
an RDF vocabulary for expressing transport metadata called <a 
href="http://www.markbaker.ca/2003/05/RDF-Forms/">RDF Forms</a>.

Tom wishes to write a general GRDDL profile that extracts an RDF Form 
graph from the XForms submission elements employed in the various web 
forms for editing, deleting, and updating Atom entries on his weblog. 
Such a profile can uniformly extract an RDF description of the transport 
mechanisms forn a software agent to interpret.  The software agent can 
automatically retrieve an Introspection Document (via the Atom Publishing 
Protocol), update existing entries using the identified service URLs, and 
perform other such services without the necessity of a top-heavy web 
service stack to capture the service endpoints available at Tom's weblog.

Additionally, I attempted a first cut at such a profile:

http://esw.w3.org/topic/GRDDLProfileForXForms

This particular usecase overlaps a bit with (or could be the perfect segue 
for) the Atom/OWL usecase, so I tried to have the focus be on the Atom 
Publishing Protocol instead of the Atom syntax itself - which works well 
for this usecase since it emphasizes the use of XForms submission 
elements for targeting service endpoints for managing atom entries.

I hope this works.  I could possibly drill down further, but I wasn't sure 
of the level of detail we were going for with these.

Later


-- Chimezie Ogbuji

Received on Tuesday, 15 August 2006 03:35:47 UTC