- From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 19 Jul 2005 18:29:02 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv17016
Modified Files:
ws-addr-core.xml
Log Message:
Added revised resolution to issue lc68 - updated text warning designers of EPR extensions that default processing prevails when their extension is not understood
Index: ws-addr-core.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-core.xml,v
retrieving revision 1.102
retrieving revision 1.103
diff -C2 -d -r1.102 -r1.103
*** ws-addr-core.xml 12 Jul 2005 18:46:50 -0000 1.102
--- ws-addr-core.xml 19 Jul 2005 18:28:59 -0000 1.103
***************
*** 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" >
--- 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" >
***************
*** 231,235 ****
mechanism for delivery (e.g.
using a pre-existing transport
! connection) from a prior interaction.</td>
</tr>
<tr>
--- 231,235 ----
mechanism for delivery (e.g.
using a pre-existing transport
! connection from a prior interaction).</td>
</tr>
<tr>
***************
*** 436,440 ****
extended endpoint reference is processed by software that understands the
extension(s). When designing endpoint reference extensions designers should
! consider whether they desire standard processing per this specification in cases
where their extension is not recognized or understood.</p>
</div2>
--- 436,440 ----
extended endpoint reference is processed by software that understands the
extension(s). When designing endpoint reference extensions designers should
! consider that standard processing per this specification will prevail in cases
where their extension is not recognized or understood.</p>
</div2>
***************
*** 586,597 ****
properties defined in <specref ref="abstractmaps"/>:</p>
<eg xml:space="preserve">
! <<b>wsa:To</b>><i>xs:anyURI</i></<b>wsa:To</b>>
! <<b>wsa:From</b>><i>wsa:EndpointReferenceType</i></<b>wsa:From</b>>
! <<b>wsa:ReplyTo</b>><i>wsa:EndpointReferenceType</i></<b>wsa:ReplyTo</b>>
! <<b>wsa:FaultTo</b>><i>wsa:EndpointReferenceType</i></<b>wsa:FaultTo</b>>
<<b>wsa:Action</b>><i>xs:anyURI</i></<b>wsa:Action</b>>
! <<b>wsa:MessageID</b>><i>xs:anyURI</i></<b>wsa:MessageID</b>>
! <<b>wsa:RelatesTo</b> RelationshipType="<i>xs:anyURI</i>"?><i>xs:anyURI</i></<b>wsa:RelatesTo</b>>
! <<b>wsa:ReferenceParameters</b>><i>xs:any</i>*</<b>wsa:ReferenceParameters</b>>
</eg>
<p>The following describes the attributes and elements listed in the schema overview
--- 586,597 ----
properties defined in <specref ref="abstractmaps"/>:</p>
<eg xml:space="preserve">
! <<b>wsa:To</b>><i>xs:anyURI</i></<b>wsa:To</b>> ?
! <<b>wsa:From</b>><i>wsa:EndpointReferenceType</i></<b>wsa:From</b>> ?
! <<b>wsa:ReplyTo</b>><i>wsa:EndpointReferenceType</i></<b>wsa:ReplyTo</b>> ?
! <<b>wsa:FaultTo</b>><i>wsa:EndpointReferenceType</i></<b>wsa:FaultTo</b>> ?
<<b>wsa:Action</b>><i>xs:anyURI</i></<b>wsa:Action</b>>
! <<b>wsa:MessageID</b>><i>xs:anyURI</i></<b>wsa:MessageID</b>> ?
! <<b>wsa:RelatesTo</b> RelationshipType="<i>xs:anyURI</i>"?><i>xs:anyURI</i></<b>wsa:RelatesTo</b>> *
! <<b>wsa:ReferenceParameters</b>><i>xs:any</i>*</<b>wsa:ReferenceParameters</b>> ?
</eg>
<p>The following describes the attributes and elements listed in the schema overview
Received on Tuesday, 19 July 2005 18:29:05 UTC