[
Lists Home |
Date Index |
Thread Index
]
i'd put issues in composing WS-* specs down to:
1) they've not been designed to be plug-replaceable
but fit into slightly disconnected visions. e.g.
WS-Policy doesn't map directly to WSDL 2.0 Features
and Properties, you can't just swap Notification with
Eventing. OK there may possibly be mappings but there
are lots of edge conditions.
2) IPR problems: an open standard is unlikely
to reference and build on a defacto one. So we end
up with having to rely upon generalised extensibility
models. yeah, of course you can just stick tags from
different namespaces into an XML document. XML is great!
Paul
-----Original Message-----
From: Rich Salz [mailto:rsalz@datapower.com]
Sent: 07 April 2004 19:00
To: Paul Sumner Downey
Cc: xml-dev@lists.xml.org
Subject: Re: [xml-dev] Competing Specifications - A Good or Bad Thing?
> I don't think all of these WS-* specs *are* composable.
Why do you say that? We have customers using WS-Security, and some of
the tokens they define, without using other things. We've done demo's
using WS-Routing/addressing, etc. Have you found issues, or is this
just gut feeling based on your experiences?
/r$
--
Rich Salz, Chief Security Architect
DataPower Technology http://www.datapower.com
XS40 XML Security Gateway http://www.datapower.com/products/xs40.html
XML Security Overview http://www.datapower.com/xmldev/xmlsecurity.html
-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription
manager: <http://www.oasis-open.org/mlmanage/index.php>
|
