W3C home > Mailing lists > Public > www-ws-arch@w3.org > May 2002

RE: RFC: Attributes and XML-RPC

From: Anne Thomas Manes <anne@manes.net>
Date: Thu, 9 May 2002 17:31:18 -0400
To: "B Cookson" <bcookson42@yahoo.com>, <www-ws-arch@w3.org>
Message-ID: <CJEIKEMEBAONGDDNLEKFIEBEEEAA.anne@manes.net>
IMHO support for attributes is absolutely required. People want to use SOAP
to pass XML documents, and XML supports attributes. Hence SOAP must support
attributes.

Anne
  -----Original Message-----
  From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
Behalf Of B Cookson
  Sent: Thursday, May 09, 2002 5:02 PM
  To: www-ws-arch@w3.org
  Subject: Re: RFC: Attributes and XML-RPC


     In responce to discussion based on:

          a.. From: "John Tigue" <john.tigue@tigue.com>
          b.. To: <xml-dev@ic.ac.uk>
          c.. Date: Tue, 21 Sep 1999 09:17:49 -0700
Perhaps my memory fails me but I clearly remember being in
a SOAP meeting at Microsoft where a very wrong headed gentleman
from Redmond (name withheld to protect the confused)
responding to my question "why no attributes". One high
profile XML guy from Microsoft who was present at the
meeting was taken aback by the decisions made. The first
gentleman expressed the opinion that attributes in general were
an unnecessary redundancy in the XML spec and he would have
nothing to do with them in SOAP.
---------------------------------------------





      OK, not supporting attributes makes SOAP simpler in some ways.  But

      given a data or document centric Web Services model I define by Web

      Service with WSDL / XML schema.  So, according to SOAP spec, I simply
do

      not use attributes.  This is great when I create a schema from
scratch,

      but the problem I have is often I want to use existing schema already
in

      common use for the type of data my Web Service is dealing with.  For

      example I want to build a MyData Web Service to pass around messages
with

      MyData documents.  But the pre-existing MyData schema uses attributes

      which are lost when sent via Web Service frameworks.



      This does not simplify, this create a problem that I must invent a new

      redundant schema only because the message communication system (SOAP)
does not support attributes although the business processes on either side
do.

      Must I create a special "transport within SOAP schema?" which encodes
attributes as elements?  How are people currently dealing with this

      problem?



      --Bennett Cookson







----------------------------------------------------------------------------
--
  Do You Yahoo!?
  Yahoo! Shopping - Mother's Day is May 12th!
Received on Thursday, 9 May 2002 17:31:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:24:59 GMT