CARVIEW |
Select Language
HTTP/2 200
date: Tue, 07 Oct 2025 15:33:05 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 20 Jul 2023 23:26:50 GMT
cache-control: max-age=2592000, public
expires: Thu, 06 Nov 2025 15:33:05 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98ae746ebbee0bc9
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: MISS
set-cookie: __cf_bm=LPZvtbHx8y4NZ6kCLqRP079Kksi3FXO_Kf7w.x1GLJM-1759851185-1.0.1.1-JU6tU8QHkHBP7mhG1L.X6iOBL7jfkPY6Dq7UgAnuYL6Ep.0ViCdMkUVqy5fTUu7u0RY2KtSlelEexVxnpYV6qBVaOJng7SklL9D1RvQ.JyA; path=/; expires=Tue, 07-Oct-25 16:03:05 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98ae746ebbee0bc9-BLR
alt-svc: h3=":443"; ma=86400
Re: Issue 210: component equivalence from Mark Nottingham on 2004-06-22 (www-ws-desc@w3.org from June 2004)
Re: Issue 210: component equivalence
- From: Mark Nottingham <mark.nottingham@bea.com>
- Date: Mon, 21 Jun 2004 17:13:29 -0700
- To: Roberto Chinnici <Roberto.Chinnici@Sun.COM>
- Cc: www-ws-desc@w3.org
- Message-Id: <FCF11F81-C3E0-11D8-AB5E-000A95BD86C0@bea.com>
On Jun 21, 2004, at 4:58 PM, Roberto Chinnici wrote: > Given that different top-level components must have different names, > if you process a valid WSDL document and get some components out of it, > you can decide whether two top-level components are equivalent just > by comparing their {name} properties. Oh, OK. how about: --8<-- Note that because different top-level components (e.g., interface, binding and service) are required to have different names, it's possible to determine whether two of a given type are equivalent by examining their {name} and {target namespace} properties. -->8-- Thanks, -- Mark Nottingham Principal Technologist Office of the CTO BEA Systems
Received on Monday, 21 June 2004 20:13:31 UTC