Subject: WG last call - still some invalid XML

From: Nicolas Popp <[email-masked]>
Date: Wed, 18 Oct 2000 13:27:53 -0700

A detailed bug report from one of our engineers (who uses a better XML
editor than any of us!) ...

-Nico

> 1. Page 12, Invalid XML sample:
>
>    <results>
>         <service id="i0">
>              <serviceuri>http://cnrp.bar.com/</serviceuri>
>         </service>
>         <resourcedescriptor id="i1">
>              <commonname>bmw</commonname>
>              <id>foo.com:234364</id>
>              <resourceuri>http://www.bmw.de/</resourceuri>
>              <property name="language" type="rfc1766">de-DE</property>
>         </resourcedescriptor>
>         <referral>
>              <serviceref ref="i0" />
>         </referral>
>    </results>
>
> *     resourcedescriptor MUST have (according to DTD) serviceref and
> description elements!
>
>
> 2. Page 14, Invalid XML sample:
>
>    <service id="i0">
>        <serviceuri>http://acmecorp.com</serviceuri>
>        <dataset id="i1">
>            <property
> name="dataseturi">urn:oid:1.2.3.4.666.5.4.3.1</property>
>            <property name="language">en-us</property>
>            <property name="language">en-gb</property>
>            <description>This is an example of a complex CNRP service
>            </description>
>        </dataset>
>        <dataset id="i2">
>            <property
> name="dataseturi">urn:oid:1.2.3.4.666.10.9.8.7.6</property>
>            <property name="language">fr</property>
>        </dataset>
>    </service>
>
> *     there should be no description element inside dataset!
>
>
> 3. Page 16-17, Invalid XML sample:
>
>         <results>
>              <service id="i0">
>                   <serviceuri>http://acmecorp.com</serviceuri>
>                   <dataset id="i1">
>                      <property name="dataseturi">
>                  urn:oid:1.2.3.4.666.5.4.3.1
>                      </property>
>                   </dataset>
>                   <dataset id="i2">
>                      <property name="dataseturi">
>                       urn:oid:1.2.3.4.666.10.9.8.7.6
>                      </property>
>                   </dataset>
>              </service>
>              <service id="i3">
>                 <serviceuri>http://serverfarm.acmecorp.com</serviceuri>
>              </service>
>              <service id="i4">
>                  <serviceuri>http://servers.acmecorp.co.uk</serviceuri>
>                  <dataset id="i4">
>                      <property name="dataseturi">
>                        urn:oid:1.2.3.4.666.5.4.3.1
>                      </property>
>                  </dataset>
>              </service>
>              <resourcedescriptor>
>                        <commonname>Fidonet</commonname>
>                        <id>1333459455</id>
>                        <resourceuri>http://www.fidonet.ca</resourceuri>
>                        <serviceref ref="i0" /><datasetref ref="i1" />
>                        <description>This is ye olde Canadian
>                         Fidonet</description>
>              </resourcedescriptor>
>              <resourcedescriptor>
>                        <commonname>Fidonet</commonname>
>                        <id>1333459455</id>
>                        <resourceuri>http://host:port/bla</resourceuri>
>                        <serviceref ref="i1" />
>              </resourcedescriptor>
>              <referral>
>                  <serviceref id="i0" /><datasetref ref="i2" />
>              </referral>
>         </results>
>
> *     id attributes are duplicated for <service id="i4"> and <dataset
> id="i4">
> *     the second resource descriptor's is plagued with following:
> *     description element is missing
> *     serviceref ref attribute is pointing to dataset not service element
> (i4)
> *     referral's element serviceref has invalid attribute id (it should be
> ref according to DTD)
>
>
> 4. Page 17 - Invalid XML sample:
>
>
>        <results>
>             <status code="x.y.z" ref="i2">
>                  The CNRP foo.com database is temporarily unreachable
>             </status>
>        </results>
>
> *      there is no other element that status can reference here!
>
> 5. Page 19 - Invalid XML sample:
>
>    <results>
>         <service id="i0">
>              <serviceuri>http://cnrp.bar.com/</serviceuri>
>              <property name="dataseturi">
>                   urn:oid:1.3.6.1.4.1.782.1
>              </property>
>              <property name="dataseturi">
>                   urn:oid:1.3.6.1.4.1.782.2
>              </property>
>         </service>
>         <resourcedescriptor>
>              <commonname>bmw</commonname>
>              <property name="language" type="iso646">de-DE</property>
>              <id>foo.com:234364</id>
>              <resourceuri>http://www.bmw.de/</resourceuri>
>         </resourcedescriptor>
>         <referral>
>              <serviceref ref="i0" />
>              <property name="dataseturi">
>                   urn:oid:1.3.6.1.4.1.782.2
>              </property>
>         </referral>
>    </results>
>
> *     resourcedescriptor MUST have (according to DTD) serviceref and
> description elements!
> *     property element should be the last element in resourcedescriptor
> *     there should be no property elements inside referral element
>
>
> 6. Page 22 - Invalid XML sample:
>
>    <service>
>         <propertyschema>
>            <propertydeclaration id="i1">
>                  <propertyname>language</propertyname>
>                  <propertytype>rfc1766<propertytype>
>            </propertydeclaration>
>            <propertydeclaration id="i2">
>                  <propertyname>cocktailrecipe</propertyname>
>                  <propertytype>freeform<propertytype>
>            </propertydeclaration>
>         </propertyschema>
>         <queryschema>
>              <propertyreference required="yes" idref="i1"/>
>         </queryschema>
>         <resourcedescriptorschema>
>              <propertyreference required="yes" idref="i1"/>
>              <propertyreference required="yes" idref="i2"/>
>         </resourcedescriptorschema>
>    </service>
>
> *     service element MUST have serviceuri element!
> *     propertytype elements are not closed!
> *     propertyreference element, attribute idref should be renamed to ref
>
>
>
> 7. Page 25 - Invalid XML sample:
>         <results>
>         <service ttl="43200">
>              <serviceuri>urn:foo:bar</serviceuri>
>              <servers>
>              <server>
>              <serveruri>http://host1.acmecorp.com:4321/foo?</serveruri>
>              </server>
>              <server>
>              <serveruri>smtp://host2.acmecorp.com:4321/foo?</serveruRI>
>              </server>
>              </servers>
>              <description>This is the AcmeCorp CNRP Service</description>
>              <!-- This property means that AcmeCorp specializes in
>                   tradename services -->
>              <property name="category" type="naics">544554</property>
>              <property name="BannerAdServer" type="uri">
>                  http://adserver.acmecorp.com/
>              </property>
>              <propertyschema>
>                   <propertydeclaration id="i1">
>                        <propertyname>workgroupID</propertyname>
>                        <propertytype default="yes">freeform</propertytype>
>                        <propertytype
> default="no">domainname</propertytype>
>                        </propertydeclaration>
>                        <propertydeclaration id="i2">
>                        <propertyname>BannerAdServer</propertyname>
>                        <propertytype default="yes">URI</propertytype>
>                   </propertydeclaration>
>              </propertyschema>
>              <queryschema>
>                   <propertyreference ref="i1" required="yes" />
>              </queryschema>
>              <resourcedescriptorschema>
>                   <propertyreference ref="i1" required="yes" />
>              </resourcedescriptorschema>
>              <serviceschema>
>                   <propertyreference ref="i2" required="yes" />
>              </serviceschema>
>         </service>
>         </results>
>
> *     misspelled end tag for the second serveruri element
>
>
> 8. Page 27 - Invalid XML sample:
>
>
>
>    <?xml version="1.0"?>
>    <!DOCTYPE cnrp PUBLIC "-//IETF//DTD CNRP 1.0//EN">
>    <cnrp>
>         <results>
>              <service id="i0">
>                   <serviceuri>http://acmecorp.com</serviceuri>
>              </service>
>              <service id="i1">
>                   <serviceuri>http://serverfarm.acmecorp.com</serviceuri>
>              </service>
>              <service id="i2">
>                    <serviceuri>http://servers.acmecorp.co.uk</serviceuri>
>              </service>
>              <resource>
>                        <commonname>Fidonet</commonname>
>                        <id>1333459455</id>
>                        <resourceuri>http://www.fidonet.ca</resourceuri>
>                        <serviceref ref="i0" />
>                        <description>This is ye olde Canadian
>                           Fidonet</description>
>              </resource>
>              <resource>
>                        <commonname>Fidonet</commonname>
>                        <id>1333459455</id>
>                        <resourceuri>http://host:port/bla</resourceuri>
>                        <serviceRef ref="i1" />
>              </resource>
>              <referral><serviceRef ref="i2" /></referral>
>              <status code="3.1.1">The language property 'fr-CA' was
> ignored</status>
>         </results>
>    </cnrp>
>
> *     resource element should be renamed to resourcedescriptor
> *     serviceref element should be spelled with all small case letters
> (two occurrences)
> *     second resourcedescriptor is missing required description element
>
>
>
>
> -----Original Message-----
> From: Leslie Daigle [mailto:[email-masked]]
> Sent: Wednesday, October 18, 2000 5:46 AM
> To: [email-masked]
> Subject: WG last call
>
>
> Howdy,
>
> I understand from the document editors that the last round of
> comments and updates have been incorporated in the documents, and
> these are now available as:
>
>         CNRP PROTOCOL SPECIFICATION
>         draft-ietf-cnrp-06.txt
>
>         The 'go'URI Scheme for the Common Name Resolution Protocol
>         draft-ietf-cnrp-uri-04.txt
>
> I'm putting these up for WG last call -- if there are any remaining
> (e.g., editorial) issues, please send comments to the list or
> the authors by Wednesday, November 3, 2000 (2 weeks from today).
>
> If there are no substantial changes required, we will then send
> these to the IESG for processing on the Standards track.
>
> Thanks,
> Leslie.
>
> --
>
> -------------------------------------------------------------------
> "Reality with a delicate splash of the imaginary...
>     ... or was that the other way around?"
>    -- ThinkingCat
>
> Leslie Daigle
> [email-masked]
> -------------------------------------------------------------------