Re: Widget Signature update

One (possibly minor) point regarding the filename rule:

At least the Widgets 1.0 P&C spec uses ABNF (RFC 5234) and refers to it, maybe this would be good also in the DigSig spec?

The rule expressed in ABNF would be something like:

signature-filename = "signature" non-zero-digit *DIGIT  ".xml"
non-zero-digit = %x31-39

Here, DIGIT is a prefabricated rule defined in RFC 5234. This rule says that in between the strings there must be at least one non-zero digit, followed by zero or more "normal" digits.

The normative reference for ABNF would be (grabbed from the P&C spec):

<dt><dfn id="abnf">[ABNF]</dfn></dt>
  <dd>RFC 5234, <a href="http://www.ietf.org/rfc/rfc5234.txt"><cite>Augmented BNF
                for Syntax Specifications: <abbr title="Augmented
                Backus-Naur Form">ABNF</abbr></cite></a>. D. Crocker  and P. Overell.
  January 2008.</dd>

--Jere

On 9.3.2009 22.51, "Hirsch Frederick (Nokia-CIC/Boston)" <Frederick.Hirsch@nokia.com> wrote:

I updated section 4 to correspond to  this:

"If the signatures list is not empty, sort the list of signatures by
the file name field in ascending numerical order (e.g.signature1.xml
followed by signature2.xml followed by signature3.xml etc)."


regards, Frederick

Frederick Hirsch
Nokia



On Mar 6, 2009, at 10:07 AM, ext Marcos Caceres wrote:

> Hi Frederick,
>
> On 3/6/09 3:59 PM, Frederick Hirsch wrote:
>> I've updated the widget signature document distributor file naming
>> convention to the following after discussing this with Josh (thanks
>> Josh):
>>
>> Naming convention for a distributor signature:
>>    |"signature" [1-9][0-9]* ".xml"|
>>
>>        *
>>
>>          Each distributor signature /MUST/ have a name consisting of
>>          the string "signature" followed by a digit in the range 1-9
>>          inclusive, followed by zero or more digits in the range 0-9
>>          inclusive and then ".xml", as stated by the BNF. An
>> example is
>>          "signature20.xml".
>>
>>        *
>>
>>          Leading zeros are disallowed in the numbers.
>>
>>        *
>>
>>          Any file name that does not match this BNF /MUST/ be
>> ignored.
>>          Thus a file named "signature01.xml" will be ignored. A
>> warning
>>          /MAY/ be generated.
>>
>>        *
>>
>>          There is no requirement that all the signature file names
>> form
>>          a contiguous set of numeric values.
>>
>>        *
>>
>>          These signatures /MUST/ be sorted numerically based on the
>>          numeric portion of the name. Thus signature2.xml preceeds
>>          signature11.xml, for example.
>>
>>
>> See draft
>> http://dev.w3.org/2006/waf/widgets-digsig/#distributor-signatures
>>
>> I also updated the notation section, changed the code format to be
>> italic (without color), and updated the body style to not be quite
>> so large.
>>
>> Please indicate any comment or corrections on the list.
>>
>
> The changes look good to me! thank you.
>
> Kind regards,
> Marcos