Re: [Simple] WGLC on RPID, CIPID and future status [Future]

[Miguel Garcia <[e-mail]>]

Hi:

Some comments about the future status draft. I read the working version 
stored at:

http://www.cs.columbia.edu/sip/draft/timed-status/draft-ietf-simple-future-02.txt

- I miss the terminology section (definition of MUST, SHOULD, etc.) and 
the reference to RFC 2119

- Section 2:

    "The <timed-status> element can only appear within a PIDF <tuple>
    element. "

   shouldn't it be normative:

   "<time-status> elements MUST only appear as children of the PIDF 
<tuple> element."


- Section 2:

    "The <timed-status> element may contain any PIDF element, <basic> and
    <note>, as well as status extensions, such as RPID [3]."

    shouldn't the "may" be a normative "MAY" ?

    "The <timed-status> element MAY contain any PIDF element, <basic> and
    <note>, as well as status extensions, such as RPID [3]."

- Section 2:

    "However, not
    all elements in PIDF extensions are sensible in this context.  For
    example, information such as contact information [4] that does not
    change as a function of time is inappropriate for use with timed
    status."

    shouldn't we add a normative statement disallowing implementations 
to use <contact> elements in combination with <time-status>? Something like:

    "<time-status> elements MUST NOT contain child <contact> elements."

- Section 2: last paragraph. Since there is a dependency between 
<time-status> and <timestamp>, shouldn't we strongly recommend to use 
<timestamp> in combination with <time-status>?

   "It is RECOMMENDED to include a PIDF <timestamp> element whenever the 
<time-status> element is included in an XML document."

- Section 3: According to the PIDF, the <contact> element is ordered 
after the extensions. Therefore, the current tuple:

         <tuple id="7c8dqui">
           <contact>sip:[e-mail]</contact>
           <status>
             <basic>open</basic>
           </status>
           <fs:time-status from="2003-08-15T10:20:00.000-05:00"
              until="2003-08-22T19:30:00.000-05:00">
              <basic>closed</basic>
           </fs:timed-status>
         </tuple>


    should be:

         <tuple id="7c8dqui">
           <status>
             <basic>open</basic>
           </status>
           <fs:time-status from="2003-08-15T10:20:00.000-05:00"
              until="2003-08-22T19:30:00.000-05:00">
              <basic>closed</basic>
           </fs:timed-status>
           <contact>sip:[e-mail]</contact>
         </tuple>

- Section 3: shouldn't the example include a PIDF <timestamp> element, 
especially if it is recommended in the text?

- Section 3: I would recommend to replace the namespace prefix "fs" by 
"ts", since it represents the current initials of the draft.

- Section 4, Schema: shouldn't the definition of "note" include a 
minOccurs of zero? Without minOccurs, this element must be present in 
the document. So I suggest to replace:

           <xs:element name="note" type="pidf:note"/>

    with

           <xs:element name="note" type="pidf:note" minOccrus="0"/>


Regards,

       Miguel

ext [e-mail] wrote:

> The WG chairs would like to start a Working Group Last Call on the following drafts as part of the SIMPLE PIDF profile to be submitted to IESG:
> 
> http://www.ietf.org/internet-drafts/draft-ietf-simple-rpid-03.txt
> http://www.ietf.org/internet-drafts/draft-ietf-simple-cipid-01.txt
> http://www.ietf.org/internet-drafts/draft-ietf-simple-future-01.txt
> 
> This WGLC will end on May 11th.
> 
> Please send your comments to this mailing list and to the authors. 
> 
> If you reviewed the draft and found no issues, please indicate so on the mailing list. This will help us evaluate the level of review and group consensus.
> 
> Thanks,
> Hisham
> 
> _______________________________________________
> Simple mailing list
> [e-mail]
> https://www1.ietf.org/mailman/listinfo/simple
> 

-- 
Miguel A. Garcia           tel:[phone]
Nokia Research Center      Helsinki, Finland


_______________________________________________
Simple mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/simple