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

2004/ws/addressing ws-addr-core.xml,1.104,1.105

From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 19 Jul 2005 19:13:54 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1DuxXO-0007OJ-JL@lionel-hutz.w3.org>

Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv28401

Modified Files:
	ws-addr-core.xml 
Log Message:
Added resolution to issue lc101, lc104 - clarified extensibility of abstract properties

Index: ws-addr-core.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-core.xml,v
retrieving revision 1.104
retrieving revision 1.105
diff -C2 -d -r1.104 -r1.105
*** ws-addr-core.xml	19 Jul 2005 18:46:56 -0000	1.104
--- ws-addr-core.xml	19 Jul 2005 19:13:52 -0000	1.105
***************
*** 1,5 ****
  <?xml version="1.0"?>
  <!-- $Id$ -->
! <!DOCTYPE spec PUBLIC "-//W3C//DTD Specification V2.1//EN" "xmlspec.dtd" [de
  <!ENTITY prefix "ws-addr-core">
  <!ENTITY % entities SYSTEM "entities.dtd" >
--- 1,5 ----
  <?xml version="1.0"?>
  <!-- $Id$ -->
! <!DOCTYPE spec PUBLIC "-//W3C//DTD Specification V2.1//EN" "xmlspec.dtd" [
  <!ENTITY prefix "ws-addr-core">
  <!ENTITY % entities SYSTEM "entities.dtd" >
***************
*** 119,123 ****
                      of {any} indicates the presence of an element wildcard
                      (&lt;xs:any/&gt;). The use of @{any} indicates the presence of an
!                     attribute wildcard (&lt;xs:anyAttribute/&gt;). In addition, where
                      pseudo-schemas are provided for a component, they use BNF-style conventions for
                      attributes and elements: "?" denotes optionality (i.e. zero or one occurrences),
--- 119,124 ----
                      of {any} indicates the presence of an element wildcard
                      (&lt;xs:any/&gt;). The use of @{any} indicates the presence of an
!                     attribute wildcard (&lt;xs:anyAttribute/&gt;).</p>
!                 <p>Where
                      pseudo-schemas are provided for a component, they use BNF-style conventions for
                      attributes and elements: "?" denotes optionality (i.e. zero or one occurrences),
***************
*** 127,131 ****
                      the normative schema. Elements with simple content are conventionally assigned a
                      value which corresponds to the type of their content, as defined in the
!                     normative schema.</p>
                  <p>When defining the cardinality of endpoint reference properties and message
                      addressing properties, this specification uses the following notation:
--- 128,133 ----
                      the normative schema. Elements with simple content are conventionally assigned a
                      value which corresponds to the type of their content, as defined in the
!                     normative schema. Pseudo schemas do not include extensibility points for
!                     brevity.</p>
                  <p>When defining the cardinality of endpoint reference properties and message
                      addressing properties, this specification uses the following notation:
***************
*** 204,208 ****
              <div2 id="eprinfomodel">
                  <head>Information Model for Endpoint References</head>
!                 <p>An endpoint reference consists of the following abstract properties:</p>
                  <glist>
                      <gitem>
--- 206,216 ----
              <div2 id="eprinfomodel">
                  <head>Information Model for Endpoint References</head>
!                 <p>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 and/or add 
!                     other properties.  The semantics and XML Infoset representation 
!                     for any such extension properties will be described in their defining 
!                     specifications.
!                     An endpoint reference consists of the following abstract properties:</p>
                  <glist>
                      <gitem>
***************
*** 387,390 ****
--- 395,403 ----
                      </gitem>
                  </glist>
+                 <note><p>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 <specref
+                         ref="eprinfomodel"/>.</p></note>
                  <p>The following shows an example endpoint reference. This element references the
                      the endpoint at the URI "http://example.com/fabrikam/acct".</p>
Received on Tuesday, 19 July 2005 19:14:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:19:40 GMT