W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > January 2009

[Bug 6433] New: WS-Transfer and WS-MetadataExchange schemas contain weakly-typed EPRs

From: <bugzilla@wiggum.w3.org>
Date: Wed, 14 Jan 2009 20:57:08 +0000
To: public-ws-resource-access-notifications@w3.org
Message-ID: <bug-6433-2780@http.www.w3.org/Bugs/Public/>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=6433

           Summary: WS-Transfer and WS-MetadataExchange schemas contain
                    weakly-typed EPRs
           Product: WS-Resource Access
           Version: PR
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Transfer
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: gilbert.pilz@oracle.com


WS-Transfer and WS-Mex both have schemas that define EPR types that look
something like:

  <xs:element name="FlexibleEPR">
    <xs:complexType>
      <xs:sequence>
        <xs:any minOccurs='1' maxOccurs='unbounded' processContents='skip'
namespace='##other' />
      </xs:sequence>
    </xs:complexType>
  </xs:element>

Since we have agreed that is *not* a goal of WS-RA to support the Member
Submission version of WS-Addressing (200408), these weakly-typed EPRs are
unnecessary. Since, in this context, weak types are inferior to strong types
(interoperability, message validation, code generation, etc.) these types
should be removed and references to them changed to refer to the WS-Addressing
1.0 defined EPR type (i.e. wsa:EndpointReferenceType).

Proposal: Remove weak EPRs from WS-T and WS-Mex and replace them with
wsa:EndpointReferenceType.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
Received on Wednesday, 14 January 2009 21:03:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:26 GMT