- From: Jeremy Carroll <jjc@hpl.hp.com>
- Date: Mon, 19 Mar 2007 13:49:44 +0000
- To: GRDDL Working Group <public-grddl-wg@w3.org>
Doc reviewed: http://www.w3.org/2001/sw/grddl-wg/doc43/scenario-gallery.htm $Id: scenario-gallery.htm,v 1.78 2007/03/14 14:47:06 jigsaw Exp $ Summary: ======== - ready for publication - why not straight to WG Note, so that we have no more work on this? - need to decide about http headers use case - a couple of minor editorial issues Editorial suggestions ===================== 1) delete number 1 on Introduction header. 2) In introduction, excerpt entitled RDF/XML Suggest replace: <dc:subject>ADAM; Simple Search; Index+; prototype</dc:subject> with <dc:subject >ADAM; Simple Search; Index+; prototype</dc:subject> to avoid line breaking in the string. (looks worse though, I am happy for the editor to ignore this). HTTP header =========== It says: [[ This use-case uses a feature at risk that is dependent on the HTTP Header Linking Draft being accepted to the IETF as an RFC. If it is not accepted by March 31st 2007, the feature and the use-case will be removed. ]] we are confident that this will not happen, so we could simply delete the section. May be better to change that para to something like: [[ This use-case uses a feature that is not, and will not be, included in the GRDDL Working Draft. It should be addressable in the future using the mechanims described in the HTTP Header Linking Draft once that is accepted by the IETF as an RFC. ]] That would be my preference. If this was done the final para: [[ Using the ability of GRDDL to specify Link and Profiles for GRDDL transformation in HTTP Headers, Oceanic Consortium can serve RDF via GRDDL without altering their XML documents. ]] would need to be changed to [[ Using the ability of HTTP Header Linking Draft to specify Link and Profiles for GRDDL transformation in HTTP Headers, Oceanic Consortium can serve RDF via GRDDL without altering their XML documents. ]] WG Note? ======== To reduce our workload, this document can go straight to WG Note, in my view. The require changes would be: - changes to conform to WG Note style - change to SOTD, for example, as follows, which simplifies the previous SOTD. <div> <h2 id="Status">Status of this Document</h2> <p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/" shape="rect">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p> <p> This document is a Working Group Note, developed by the <a href="http://www.w3.org/2001/sw/grddl-wg/">GRDDL Working Group</a>. </p> <p>As of the publication of this Working Group Note the <a href="http://www.w3.org/2001/sw/grddl-wg/">GRDDL Working Group</a> has completed work on this document. Changes from the previous Working Draft are indicated in a <a href="#changes">log of changes</a>. Comments on this document may be sent to <a href="mailto:public-grddl-comments@w3.org">public-grddl-comments@w3.org</a> (with <a href="http://lists.w3.org/Archives/Public/public-grddl-comments/">public archive</a>). Further discussion on this material may be sent to the Semantic Web Interest Group mailing list, <a href="mailto:semantic-web@w3.org">semantic-web@w3.org</a> (also with <a href="http://lists.w3.org/Archives/Public/semantic-web/">public archive</a>). </p> <p>Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress</p> <p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/" shape="rect">5 February 2004 W3C Patent Policy</a>. This document is informative only. W3C maintains a <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/39407/status">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. </p> </div> Jeremy PS This document was of a significantly higher quality than I expected.
Received on Monday, 19 March 2007 13:50:07 UTC