Re: GRDDL-aware agents (Was Re: "GRDDL Agents" ...) (#issue-conformance-labels)

OK, I've integrated feedback from this thread into...

http://www.w3.org/2004/01/rdxh/spec#sec_agt

Revision 1.226  2007/02/20 19:15:17  connolly
- go back to GRDDL-aware agents
- give example GRDDL-aware agent policy options
- be explicit about avoiding loops in recursion


Here's a copy for convenience:

---8<---


    8. GRDDL-Aware Agents

A GRDDL-aware agent is a software module that computes *GRDDL results* 
of information resources.

For example, a SPARQL query service might use a GRDDL-aware agent for 
collecting RDF data. Or a Web browser might serve as a GRDDL-aware agent 
for the purpose of collecting calendar and contact data. The appropriate 
policy for which results to compute and when is likely to involve 
waiting for a signal from user more in the Web browser case than in the 
query service case.

Subject to security considerations 
<http://www.w3.org/2004/01/rdxh/spec#sec> below and local policy as 
expressed in its configuration, given a URI I of an information resource 
IR, and an XPath node N for a representation of IR, a GRDDL Agent *should*:

   1. Find each transformation associated with N, i.e.
         1. each transformation associated with N via the
            grddl:transformation attribute as in the Adding GRDDL to
            well-formed XML
            <http://www.w3.org/2004/01/rdxh/spec#grddl-xml> section
         2. each transformation associated with N via HTML links of type
            transformation, provided the document bears the
            http://www.w3.org/2003/g/data-view profile, as in the Using
            GRDDL with valid XHTML
            <http://www.w3.org/2004/01/rdxh/spec#grddl-xhtml> section.
         3. each transformation associated with N via HTTP links of type
            transformation, provided the message bears the
            http://www.w3.org/2003/g/data-view profile, as in the Using
            GRDDL with HTTP
            <http://www.w3.org/2004/01/rdxh/spec#grddl-http> section.
         4. each transformation indicated by any available namespace
            document, as in the GRDDL for XML Namespaces
            <http://www.w3.org/2004/01/rdxh/spec#ns-bind> section.
         5. each transformation indicated by any XHTML profiles, as in
            the GRDDL for HTML Profiles
            <http://www.w3.org/2004/01/rdxh/spec#profile-bind> section.
   2. Apply each transformation to obtain a GRDDL result.
   3. Merge those GRDDL results.

Note that steps 4 and 5 are recursive; Loops in the profile/namespace 
structure should be detected in order to avoid infinite recursion.

---8<---



-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/

Received on Tuesday, 20 February 2007 19:19:16 UTC