PIDF - some things left out of draft

I think a few things need to be corrected in the draft.

Issue 1. section 4.2.4 - basic element is optional, but text implies it is
required.
4.2.4 says "In order that some level of interoperability be maintained with
user agents that don't recognise the new extension, the <basic> status value
must also be included."  That sounds like it is saying the basic element is
required, but recent mail says it is optional.

--------------

Issue 2. Extension elements from another namespace are allowed only in
specific places, but except for the status element, the text doesn't specify
where those extensions are allowed (only the schema does).  The text in
section 4.2.3 implies extensions could happen anywhere.  

To correct this, I think the following text should be added:  

Section 4.1.1, the second sentence of the first paragraph should be changed
to: "This element contains one or more <tuple> elements, followed by 0 or
more OPTIONAL <note> elements, followed by 0 or more OPTIONAL extension
elements from other namespaces."

Section 4.1.2, the second sentence of the first paragraph should be changed
to: "Thus, it contains one mandatory <status> element, followed by 0 or more
optional extension elements from other namespaces, followed by 0 or 1
OPTIONAL <contact> elements, followed by 0 or more OPTIONAL <note> elements,
followed by 0 or 1 optional <timestamp> elements."

Section 4.1.3, the first sentence of the first paragraph should be changed
to: "The <status> element contains 0 or 1 OPTIONAL <basic> elements,
followed by 0 or more OPTIONAL extension elements from other namespaces."

Section 4.2.3, the following sentence should be added before the first
sentence of the first paragraph: "Extension elements from other namespaces
can be included only as specified above as children of the <presence>,
<tuple> and <basic> elements."

-------------

Issue 3 - lines left out of schema

The following should be included just before the presence element
description ("<xs:element name="presence"...).  It is necessary for xml:lang
attributes to validate - otherwise the schema cannot be used to validate the
examples.

    <!-- This import brings in the XML language attribute xml:lang-->
    <xs:import namespace="http://www.w3.org/XML/1998/namespace"   
        schemaLocation="http://www.w3.org/2001/xml.xsd"/>

In order to allow extensions as children of the presence element, the
following should be added just before 
"</xs:sequence>" in the type definition for the presence element
("<xs:complexType name="presence">").

            <xs:any namespace="##other" processContents="lax" minOccurs="0"
               maxOccurs="unbounded"/>




  [reminder: [email protected] for non-technical discussions, please]