Re: Formal Request: WG Approval of updated Primer and Framework Errata

>
> Thanks Felix
>
> So if we simply wish to update the Primer Note itself, which might be
> simpler and clearer, is that a slow difficult process or simple and
> fast?


step 1: prepare the draft (you have done that?)
step 2: make a publication request (I would do that)

It really depends on what the WG wants to do.

Felix

>
> regards, Frederick
>
> Frederick Hirsch
> Nokia
>
>
>
> On Nov 22, 2008, at 12:34 AM, ext Felix Sasaki wrote:
>
>> Felix Sasaki さんは書きました:
>>>
>>> Hello Frederick,
>>>
>>> just FYI:
>>>
>>> Frederick Hirsch さんは書きました:
>>>> Attached are an update to the Framework Errata document, and a new
>>>> Primer Errata document.
>>>>
>>>> This message is requesting the chairs and WG for formal WG
>>>> approval of these documents and publication.
>>>>
>>>> Once approved they can be checked into CVS [1]. This will update
>>>> the content referenced from the Framework Recommendation [2] to
>>>> the Framework Errata, making the Framework errata visible.
>>>>
>>>> The Primer Note does not have a link to the errata. I recommend
>>>> that the WS-Policy WG home page [3] be updated with a link to the
>>>> Errata document for the Primer.
>>>
>>> From the W3C process you can have an errata document only for
>>> Recommendations. However, if the WG is fine to maintain a document
>>> like what your propose, that's fine. You just have to be aware of
>>> the informal status of that document.
>>>
>>>>
>>>> Separately I ask whether we might also update the note to include
>>>> a link to the primer errata document.
>>>
>>> I'm not sure if that is OK - to publish a WG Note with a link to an
>>> errata document. I'll check and come back to you.
>>
>> I checked, it's OK to publish a new version of the Note that links
>> to the errata
>> document. Meanwhile, if there are primer errata, you may take the
>> opportunity to integrate them.
>>
>>
>> Felix
>>
>>>
>>> Felix
>>>
>>>>
>>>> Thanks to Asir for reviewing drafts of the errata documents.
>>>>
>>>> regards, Frederick
>>>>
>>>> Frederick Hirsch
>>>> Nokia
>>>>
>>>> [1] they would both be checked into the directory WWW/2002/ws/
>>>> policy/7 in /w3ccvs
>>>>
>>>> [2] http://www.w3.org/TR/2007/REC-ws-policy-20070904/
>>>>
>>>> [3] http://www.w3.org/2002/ws/policy/ , Add errata link next to
>>>> entry in bullet list for primer
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>> W3C <http://www.w3.org/>
>>>>
>>>>
>>>>  Web Services Policy 1.5 - Framework Errata
>>>>
>>>>
>>>>    21 November 2008
>>>>
>>>> Latest version:
>>>>    http://www.w3.org/2002/ws/policy/7/framework-errata.html Editors:
>>>>    Asir S Vedamuthu, Microsoft Corporation
>>>>    David Orchard, BEA Systems, Inc.
>>>>    Frederick Hirsch, Nokia
>>>>    Maryann Hondo, IBM Corporation
>>>>    Prasad Yendluri, webMethods (A subsidiary of Software AG)
>>>>    Toufic Boubez, Layer 7 Technologies
>>>>    &#65533;mit Yal&#65533;inalp, SAP AG.
>>>>
>>>> Last modified: $Date: 2007/09/25 03:43:31 $
>>>>
>>>> Copyright <http://www.w3.org/Consortium/Legal/ipr-
>>>> notice#Copyright> (&#65533;) 2007 W3C <http://www.w3.org/>^&#65533;
(MIT <http://www.csail.mit.ed
>>>> u/>, ERCIM <http://www.ercim.org/>, Keio <http://www.keio.ac.jp/
>>>> >), All Rights Reserved. W3C liability
>>>> <http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer
>>>> >, trademark
>>>> <http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks
>>>> > and document use
>>>> <http://www.w3.org/Consortium/Legal/copyright-documents
>>>> > rules apply.
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>>    Abstract
>>>>
>>>> This document records all known errors in the Web Services Policy
>>>> 1.5 - Framework <http://www.w3.org/TR/2007/REC-ws-policy-20070904/
>>>> > specification; for updates see the latest version of that
>>>> document.
>>>>
>>>> The errata are numbered, classified as Substantive <#substantive>
>>>> or Editorial <#editorial>, and listed in reverse chronological
>>>> order of their date of publication in each category.
>>>>
>>>> Each entry has the following information:
>>>>
>>>>    * A unique entry number
>>>>    * The date it was added to the errata page.
>>>>    * The section referred to.
>>>>    * A description of the problem and correction if applicable.
>>>>      Changes to the text of the spec are indicated thus: deleted
>>>>      text, new text, modified text .
>>>>    * A rationale for making the change (not required for editorial
>>>>      errata).
>>>>
>>>> Changes to the text of the specification are indicated thus: new,
>>>> added text, modified text, and deleted text. Substantive
>>>> corrections are proposed by the Web Services Policy Working Group
>>>> <http://www.w3.org/2002/ws/policy/
>>>> > (part of the Web Services Activity <http://www.w3.org/2002/ws/
>>>> >), which has consensus that they are appropriate; they are not to
>>>> be considered normative until approved by a Call for Review of
>>>> Proposed Corrections
>>>> <http://www.w3.org/2004/02/Process-20040205/tr.html#cfr-corrections
>>>> > or a Call for Review of an Edited Recommendation
>>>> <http://www.w3.org/2004/02/Process-20040205/tr.html#cfr-edited
>>>> >.
>>>>
>>>> The Working Group is tracking all comments via Bugzilla
>>>> <http://www.w3.org/Bugs/Public/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=WS-Policy&component=Framework&component=Framework%2BAttachment&component=Framework%2BAttachment%2BGuidelines&component=Framework%2BAttachment%2BPrimer
>>>> > and highly prefers to receive comments via this system. If
>>>> access to Bugzilla is not feasible, you may send your comments to
>>>> the mailing list public-ws-policy-comments@w3.org
>>>> <mailto:public-ws-policy-comments@w3.org
>>>> > mailing list (public archive
>>>> <http://lists.w3.org/Archives/Public/public-ws-policy-comments/
>>>> >). Each Bugzilla entry and email message should contain only one
>>>> comment. All comments on this specification should be made
>>>> following the Description for Issues
>>>> <http://www.w3.org/2002/ws/policy/#issues
>>>> > of the Working Group. It will be very helpful if you include the
>>>> string [WS-Policy-errata] in the subject line of your comment.
>>>>
>>>>
>>>>    Status of this Document
>>>>
>>>> This document records all known errors in the Web Services Policy
>>>> 1.5 - Framework <http://www.w3.org/TR/2007/REC-ws-policy-20070904/
>>>> > specification; that were known at the time of publication of
>>>> this document.
>>>>
>>>> None of the errata reported in this document have been approved by
>>>> a Call for Review of Proposed Corrections or a Call for Review of
>>>> an Edited Recommendation. As a consequence, they must not be
>>>> considered to be normative.
>>>>
>>>>
>>>>    Table of Contents
>>>>
>>>> 1 Substantive Errata <#substantive>
>>>> 2 Editorial Errata <#editorial>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>>    1 Substantive Errata
>>>>
>>>> No substantive errata at present
>>>>
>>>>
>>>>    2 Editorial Errata
>>>>
>>>>
>>>>      E01
>>>>
>>>> Date Added: 2008-11-21
>>>>
>>>> Summary: Note on using xml:id should reference Canonical XML 1.1
>>>> and XML Signature, Second Edition. References should be updated.
>>>>
>>>>
>>>>        Section *4.2, Policy Identification*
>>>>        <http://www.w3.org/TR/2007/REC-ws-policy-20070904/#Policy_Identification
>>>> >
>>>>
>>>>  1.
>>>>
>>>>      Replace the text of the second Note
>>>>
>>>>          *Note:*
>>>>          Canonical XML 1.1 [C14N11
>>>>          <http://www.w3.org/TR/2007/REC-ws-policy-20070904/#C14N11>]
>>>>          is intended to address the issues that occur with Canonical
>>>>          XML 1.0 with regards to xml:id. The W3C XML Security
>>>>          Specifications Maintenance WG has been chartered to address
>>>>          how to integrate Canonical XML 1.1 with XML Security,
>>>>          including XML Signature [SecSpecMaintWG
>>>>          <http://www.w3.org/TR/2007/REC-ws-policy-20070904/#SecSpecMaintWG
>>>> >]
>>>>          (See http://www.w3.org/2007/xmlsec/.)
>>>>      with the following text:
>>>>
>>>>          *Note:*
>>>>          Note that is acceptable to sign a policy expression
>>>>          identified using xml:id with XML SIgnature (Second Edition)
>>>>          [XML-Signature-2ndEdition] and Canonical XML 1.1 [C14N11],
>>>>          as these recommendations address issues related to the use
>>>>          of xml:id and xml:base.
>>>>      where XML-Signature-2ndEdition is a link to a new reference
>>>>      added to the document.
>>>>
>>>>
>>>>        Appendix *B.2 Other References*
>>>>        <http://www.w3.org/TR/2007/REC-ws-policy-20070904/#Informative-References
>>>> >
>>>>
>>>>  1.
>>>>
>>>>      Update the reference to C14N11, as follows:
>>>>
>>>>          Canonical XML 1.1, J. Boyer and G. Marcy Authors. W3C
>>>>          Candidate Recommendation, 21 June 2007. This is a work in
>>>>          progress. This version is available at
>>>>          http://www.w3.org/TR/2007/CR-xml-c14n11-20070621.2 May
>>>> 2008.
>>>>          This version is available at
>>>>          http://www.w3.org/TR/2008/REC-xml-c14n11-20080502. The
>>>>          latest version of Canonical XML 1.1 is available at
>>>>          http://www.w3.org/TR//xml-c14n11/.
>>>>  2.
>>>>
>>>>      Add a reference to XML Signature (Second Edition) after the
>>>>      reference to [XMLSignature]:
>>>>
>>>>          [XML-Signature-2ndEdition] XML Signature Syntax and
>>>>          Processing, D. Eastlake, J. Reagle, D. Solo, F. Hirsch, and
>>>>          T. Roessler Editors. W3C Recommendation, 10 June 2008. This
>>>>          version of the XML Signature Syntax and Processing
>>>>          Recommendation is
>>>>          http://www.w3.org/TR/2008/REC-xmldsig-core-20080610/. The
>>>>          latest version of XML-Signature Syntax and Processing is
>>>>          available at http://www.w3.org/TR/xmldsig-core/.
>>>>      XML-Signature-2ndEdition is a link target. Note the removal of
>>>>      the hyphen in the title of the Second Edition.
>>>>
>>>>  3.
>>>>
>>>>      Remove reference to XML Security Specifications Maintenance
>>>>      Working Group, [SecSpecMaintWG], as the text that referenced it
>>>>      has been removed as part of E01:
>>>>
>>>>          [SecSpecMaintWG] XML Security Specifications Maintenance
>>>>          Working Group , See http://www.w3.org/2007/xmlsec.
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>> W3C <http://www.w3.org/>
>>>>
>>>>
>>>>  Web Services Policy 1.5 - Primer Errata
>>>>
>>>>
>>>>    21 November 2008
>>>>
>>>> Latest version:
>>>>    http://www.w3.org/2002/ws/policy/7/primer-errata.html Editors:
>>>>    Asir S Vedamuthu, Microsoft Corporation
>>>>    David Orchard, BEA Systems, Inc.
>>>>    Frederick Hirsch, Nokia
>>>>    Maryann Hondo, IBM Corporation
>>>>    Prasad Yendluri, webMethods (A subsidiary of Software AG)
>>>>    Toufic Boubez, Layer 7 Technologies
>>>>    &#65533;mit Yal&#65533;inalp, SAP AG.
>>>>
>>>> Last modified: $Date: 2007/09/25 03:43:31 $
>>>>
>>>> Copyright <http://www.w3.org/Consortium/Legal/ipr-
>>>> notice#Copyright> (&#65533;) 2007 W3C <http://www.w3.org/>^&#65533;
(MIT <http://www.csail.mit.ed
>>>> u/>, ERCIM <http://www.ercim.org/>, Keio <http://www.keio.ac.jp/
>>>> >), All Rights Reserved. W3C liability
>>>> <http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer
>>>> >, trademark
>>>> <http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks
>>>> > and document use
>>>> <http://www.w3.org/Consortium/Legal/copyright-documents
>>>> > rules apply.
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>>    Abstract
>>>>
>>>> This document records all known errors in the Web Services Policy
>>>> 1.5 - Primer
>>>> <http://www.w3.org/TR/2007/NOTE-ws-policy-primer-20071112/
>>>> > Working Group Note ; for updates see the latest version of that
>>>> document.
>>>>
>>>> The errata are numbered, classified as Substantive <#substantive>
>>>> or Editorial <#editorial>, and listed in reverse chronological
>>>> order of their date of publication in each category.
>>>>
>>>> Each entry has the following information:
>>>>
>>>>    * A unique entry number
>>>>    * The date it was added to the errata page.
>>>>    * The section referred to.
>>>>    * A description of the problem and correction if applicable.
>>>>      Changes to the text of the spec are indicated thus: deleted
>>>>      text, new text, modified text .
>>>>    * A rationale for making the change (not required for editorial
>>>>      errata).
>>>>
>>>> Changes to the text of the specification are indicated thus: new,
>>>> added text, modified text, and deleted text.
>>>>
>>>> The Working Group is tracking all comments via Bugzilla
>>>> <http://www.w3.org/Bugs/Public/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=WS-Policy&component=Framework&component=Framework%2BAttachment&component=Framework%2BAttachment%2BGuidelines&component=Framework%2BAttachment%2BPrimer
>>>> > and highly prefers to receive comments via this system. If
>>>> access to Bugzilla is not feasible, you may send your comments to
>>>> the mailing list public-ws-policy-comments@w3.org
>>>> <mailto:public-ws-policy-comments@w3.org
>>>> > mailing list (public archive
>>>> <http://lists.w3.org/Archives/Public/public-ws-policy-comments/
>>>> >). Each Bugzilla entry and email message should contain only one
>>>> comment. All comments on this specification should be made
>>>> following the Description for Issues
>>>> <http://www.w3.org/2002/ws/policy/#issues
>>>> > of the Working Group. It will be very helpful if you include the
>>>> string [WS-Policy-errata] in the subject line of your comment.
>>>>
>>>>
>>>>    Status of this Document
>>>>
>>>> This document records all known errors in the Web Services Policy
>>>> 1.5 - Primer
>>>> <http://www.w3.org/TR/2007/NOTE-ws-policy-primer-20071112/
>>>> > Working Group Note that were known at the time of publication of
>>>> this document.
>>>>
>>>>
>>>>    Table of Contents
>>>>
>>>> 1 Substantive Errata <#substantive>
>>>> 2 Editorial Errata <#editorial>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>>    1 Substantive Errata
>>>>
>>>> No substantive errata at present
>>>>
>>>>
>>>>    2 Editorial Errata
>>>>
>>>>
>>>>      E01
>>>>
>>>> Date Added: 2008-11-21
>>>>
>>>> Summary: Note on using xml:id should reference Canonical XML 1.1
>>>> and XML Signature, Second Edition. References should be updated.
>>>>
>>>>
>>>>        Section *2.10 Referencing Policy Expressions*
>>>>        <http://www.w3.org/TR/2007/NOTE-ws-policy-primer-20071112/#Referencing_Policy_Expressions
>>>> >
>>>>
>>>>  1.
>>>>
>>>>      Replace the text of the Note
>>>>
>>>>          *Note:*
>>>>          Canonical XML 1.1 [C14N11
>>>>          <http://www.w3.org/TR/2007/REC-ws-policy-20070904/#C14N11>]
>>>>          is intended to address the issues that occur with Canonical
>>>>          XML 1.0 with regards to xml:id. The W3C XML Security
>>>>          Specifications Maintenance WG has been chartered to address
>>>>          how to integrate Canonical XML 1.1 with XML Security,
>>>>          including XML Signature [SecSpecMaintWG
>>>>          <http://www.w3.org/TR/2007/REC-ws-policy-20070904/#SecSpecMaintWG
>>>> >]
>>>>          (See http://www.w3.org/2007/xmlsec/.)
>>>>      with the following text:
>>>>
>>>>          *Note:*
>>>>          Note that is acceptable to sign a policy expression
>>>>          identified using xml:id with XML SIgnature (Second Edition)
>>>>          [XML-Signature-2ndEdition] and Canonical XML 1.1 [C14N11],
>>>>          as these recommendations address issues related to the use
>>>>          of xml:id and xml:base.
>>>>      where XML-Signature-2ndEdition is a link to a new reference
>>>>      added to the document.
>>>>
>>>>
>>>>        Appendix *C References*
>>>>        <http://www.w3.org/TR/2007/NOTE-ws-policy-primer-20071112/#references
>>>> >
>>>>
>>>>  1.
>>>>
>>>>      Update the reference to C14N11, as follows:
>>>>
>>>>          Canonical XML 1.1, J. Boyer and G. Marcy Authors. W3C
>>>>          Candidate Recommendation, 21 June 2007. This is a work in
>>>>          progress. This version is available at
>>>>          http://www.w3.org/TR/2007/CR-xml-c14n11-20070621.2 May
>>>> 2008.
>>>>          This version is available at
>>>>          http://www.w3.org/TR/2008/REC-xml-c14n11-20080502. The
>>>>          latest version of Canonical XML 1.1 is available at
>>>>          http://www.w3.org/TR//xml-c14n11/.
>>>>  2.
>>>>
>>>>      Add a reference to XML Signature (Second Edition) after the
>>>>      reference to [C14N11]:
>>>>
>>>>          [XML-Signature-2ndEdition] XML Signature Syntax and
>>>>          Processing, D. Eastlake, J. Reagle, D. Solo, F. Hirsch, and
>>>>          T. Roessler Editors. W3C Recommendation, 10 June 2008. This
>>>>          version of the XML Signature Syntax and Processing
>>>>          Recommendation is
>>>>          http://www.w3.org/TR/2008/REC-xmldsig-core-20080610/. The
>>>>          latest version of XML-Signature Syntax and Processing is
>>>>          available at http://www.w3.org/TR/xmldsig-core/.
>>>>      XML-Signature-2ndEdition is a link target. Note the removal of
>>>>      the hyphen in the title of the Second Edition.
>>>>
>>>>  3.
>>>>
>>>>      Remove reference to XML Security Specifications Maintenance
>>>>      Working Group, [SecSpecMaintWG], as the text that referenced it
>>>>      has been removed as part of E01:
>>>>
>>>>          [SecSpecMaintWG] XML Security Specifications Maintenance
>>>>          Working Group , See http://www.w3.org/2007/xmlsec.
>>>>
>>>
>>>
>>>
>>
>>
>
>
>

Received on Sunday, 23 November 2008 02:25:20 UTC