Subject: Re: [Simple] Last Call: 'The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)' to Proposed Standard

From: Jonathan Rosenberg <[email-masked]>
Date: Mon, 31 Jan 2005 16:30:29 -0500

Pete,

Apologies for the delayed response. I am updating the document now.

You are absolutely correct that the schema types should instead be emty 
elements. I have corrected it per your suggestion.

Thanks,
Jonathan R.

Pete Cordell wrote:

> I haven't followed XCAP, but I wonder if the following XML schema types
> should be empty elements (e.g. <not-well-formed/>) rather than ur-type (e.g.
> <not-well-formed>blah<foo/>etc</not-well-formed>)?
> 
>     <xs:element name="not-well-formed" substitutionGroup="error-element">
>     </xs:element>
>     <xs:element name="constraint-failure" substitutionGroup="error-element">
>     </xs:element>
>     <xs:element name="cannot-delete">
>     </xs:element>
> 
> If some of them are meant to be empty, then the syntax is:
> 
>     <xs:element name="not-well-formed" substitutionGroup="error-element">
>       <xs:complexType/>
>     </xs:element>
>     <xs:element name="constraint-failure" substitutionGroup="error-element">
>       <xs:complexType/>
>     </xs:element>
>     <xs:element name="cannot-delete">
>       <xs:complexType/>
>     </xs:element>
> 
> Regards,
> 
> Pete.
> --
> =============================================
> Pete Cordell
> Tech-Know-Ware
> http://www.tech-know-ware.com/lmx
> For LMX XML to C++ binding
> (or http://www.xml2cpp.com)
> =============================================
> 
> ----- Original Message ----- 
> From: "The IESG" <[email-masked]>
> To: "IETF-Announce" <[email-masked]>
> Cc: <[email-masked]>
> Sent: Thursday, December 09, 2004 9:26 PM
> Subject: [Simple] Last Call: 'The Extensible Markup Language (XML)
> Configuration Access Protocol (XCAP)' to Proposed Standard
> 
> 
> 
>>The IESG has received a request from the SIP for Instant Messaging and
>>Presence Leveraging Extensions WG to consider the following document:
>>
>>- 'The Extensible Markup Language (XML) Configuration Access Protocol
> 
> (XCAP) '
> 
>>   <draft-ietf-simple-xcap-05.txt> as a Proposed Standard
>>
>>The IESG plans to make a decision in the next few weeks, and solicits
>>final comments on this action.  Please send any comments to the
>>[email-masked] or [email-masked] mailing lists by 2004-12-28.
>>
>>The file can be obtained via
>>http://www.ietf.org/internet-drafts/draft-ietf-simple-xcap-05.txt
>>
>>
>>_______________________________________________
>>Simple mailing list
>>[email-masked]
>>https://www1.ietf.org/mailman/listinfo/simple
> 
> 
> 
> _______________________________________________
> Simple mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/simple
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
[email-masked]                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

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