DR 11-0030, DR 11-0031, DR 11-0032

[John Haug]

Only one subsequent comment.  Let's discuss on the January 5 call, assuming there is extra time.

-----Original Message-----
From: eb2mmrt at gmail.com [mailto:eb2mmrt at gmail.com] On Behalf Of MURATA Makoto
Sent: Monday, December 12, 2011 6:13 PM
To: John Haug
Cc: e-SC34-WG4 at ecma-international.org
Subject: Re: DR 11-0030, DR 11-0031, DR 11-0032

John,

> I'd rather not add new references to incomplete works, particularly since it changes existing text.  Even if informative, it sets an expectation and recommendation.  Further, the 1.1 components are interrelated, so until they are in a position to be picked up together, we oughtn't do anything piecemeal.  They're in final stages, so I think the more appropriate thing to do is let them complete their process.  By the time we get to looking at OPC in depth, their status may be updated.

First, wearing my convenor hat, I would like to clarify a procedural issue.  Closing a DR with actions does not necessarily lead to CORs.
We can agree on some change, close the DR, and can nevertheless postpone the change to the next revision.

OPC does have several significant problems, as reported in WG4 N207.
I personally believe that the best way to address them is revision.  But when can we start?  I am looking forward to your reply to  WG4 N207.

http://www.itscj.ipsj.or.jp/sc34/wg4/archive/sc34-wg4-2011-0206.pdf

As I wrote, the XML security RNG schema currently used in 29500-2 has absolutely no official status in W3C.  It has not been maintained.  It nevertheless sets an expectation and recommendation at present.

Regards,
Makoto

> What do the rest of you think?
>
> -----Original Message-----
> From: eb2mmrt at gmail.com [mailto:eb2mmrt at gmail.com] On Behalf Of MURATA 
> Makoto
> Sent: Friday, December 09, 2011 2:15 PM
> To: John Haug
> Cc: e-SC34-WG4 at ecma-international.org
> Subject: Re: DR 11-0030, DR 11-0031, DR 11-0032
>
> John,
>
> 2011/12/10 John Haug <johnhaug at exchange.microsoft.com>:
>> DR 11-0030 - OPC:  Obsolete version of W3C XML Digital Signature 1.0
>>
>> https://skydrive.live.com/view.aspx/Public%20Documents/2011/DR-11-003
>> 0 .docx?cid=c8ba0861dc5e4adc&sc=documents
>>
>>
>>
>> This DR requests a change in the normative reference of Part 2 §3 
>> from XMLDSig 1.0 
>> (http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/) to XMLDSig 1.1 (http://www.w3.org/TR/xmldsig-core1/).
>
> Actually, the proposal is "References XML Signature 1.1. If not 
> possible, use the second edition of XML Signature 1.0."   The second 
> edition is a recommendation.
>
> XML Signature Syntax and Processing (Second Edition) W3C 
> Recommendation 10 June 2008 available at 
> http://www.w3.org/TR/2008/REC-xmldsig-core-20080610/
>
>
>
>> DR 11-0031 - OPC: Use official RELAX NG schemas from W3C
>>
>> https://skydrive.live.com/view.aspx/Public%20Documents/2011/DR-11-003
>> 1 .docx?cid=c8ba0861dc5e4adc&sc=documents
>>
>> This DR requests a change in the informative reference to XMLDSig 
>> schema of Part 2 §E.5.2 from 
>> http://www.w3.org/Signature/2002/07/xmldsig-core-schema.rng to those 
>> in http://www.w3.org/TR/xmlsec-rngschema/.
>
> The XMLDSig  RNG schema currently used in OPC has absolutely no official status.
>
> This DR requests that an officially published schema be referenced.  It is true that this schema appears in a working draft  But since the OPC RELAX NG schemas are non-normative, I see no problems.
>
>> DR 11-0032 - OPC: XML Signature Properties
>>
>> https://skydrive.live.com/view.aspx/Public%20Documents/2011/DR-11-003
>> 2 .docx?cid=c8ba0861dc5e4adc&sc=documents
>>
>>
>>
>> This DR requests Part 2 include a normative reference to, and use, 
>> the schemas of XML Signature Properties 
>> (http://www.w3.org/TR/xmldsig-properties/).
>
> In this case, I do not know when it will become a recommendation.
>
> The following paragraphs are quoted from the introduction of this CR.
> <blockquote>
> The SignatureProperties element defined by XML Signature [XMLDSIG-CORE1] offers a means to associate property values with an XML Signature. This document defines specific properties that may be used by various applications of XML Signature, without requiring those applications to define such properties on a per case basis. This document defines how these properties are to be specified and processed when used but does not require their use - specifications that reference this document may or may not require their use.
>
> The properties defined in this document are not a breaking change to XML Signature, but warrant a new namespace for the properties themselves so that they can be used in various versions of XML Signature.
> </blockquote>
>
> How about a non-normative reference and no schema changes?
>
>
> Regards,
> Makoto
>
>
>
>>
>>
>>
>> Since all of these are in either the W3C Candidate Recommendation 
>> state (0030, 0032) or W3C Working Draft state (0031), I think it's 
>> premature and inappropriate to have the standard refer to them.  I 
>> recommend these be closed without action.
>>
>>
>>
>> John
>
>
>
> --
>
> Praying for the victims of the Japan Tohoku earthquake
>
> Makoto



-- 

Praying for the victims of the Japan Tohoku earthquake

Makoto