W3C home > Mailing lists > Public > public-ws-addressing@w3.org > July 2005

Re: LC101/LC104 - proposed text

From: Prasad Yendluri <pyendluri@webmethods.com>
Date: Wed, 13 Jul 2005 18:33:50 -0700
Message-ID: <42D5C0FE.2060508@webmethods.com>
To: Glen Daniels <gdaniels@sonicsoftware.com>
CC: public-ws-addressing@w3.org


This is pretty good. The proposed text does not seem to cover 
modification via extension of the abstract properties  already defined 
in section 2.1 (core-properties).  Was that intentional? Section 2.2 XML 
Infoset Representation explicitly shows it as allowed.

Also do we need to speak to extension attributes on properties? I had it 
covered in my original proposal as below..

"The information model of an end point reference is extensible in that 
additional properties and attributes on the properties may be added.  
See the XML Infoset model section for a formal specification of the 
extensibility points at the XML Infoset level.",

Regarding the pseudo-schema in  XML infoset section not showing the 
{any} element and the @{any} attributes, this was flagged in the LC 
issue I raised 

Thanks, Prasad

Glen Daniels wrote:

>Hi folks:
>Here's an amended proposal for LC101/104.  Replace first sentence in
>section 2.1 with:
>An endpoint reference is a collection of abstract properties.  This
>specification defines a core set of properties, but it is also possible
>for other specifications to extend these with other properties.  The
>semantics and XML Infoset representation (see next section) for any such
>extension properties will be described in their defining specifications.
>The core properties are as follows:
>With regard to the XML infoset section, I notice that we're missing
>pseudo-schema for the {any} element and the @{any} attribute - I think
>we should add that.  Then, after the last
>"/wsa:EndpointReference/@{any}" definition and before the example, we
>should add:
>NOTE: Specifications which describe any extension elements or attributes
>used to augment the above model will explain any effects those
>extensions may have on the abstract properties.  They may affect either
>the core properties or extension properties as defined in section 2.1.
>I think this gets across what we discussed on Monday.
Received on Thursday, 14 July 2005 01:35:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:10 UTC