W3C home > Mailing lists > Public > www-ws-desc@w3.org > September 2003

FW: small updates/rewordings to the report from the Attributes Ta sk Force

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Wed, 3 Sep 2003 12:06:17 -0700
Message-ID: <DF1BAFBC28DF694A823C9A8400E71EA2FD7640@RED-MSG-30.redmond.corp.microsoft.com>
To: <www-ws-desc@w3.org>
Redirecting to public list.

-----Original Message-----
From: w3c-ws-desc-request@w3.org [mailto:w3c-ws-desc-request@w3.org] On
Behalf Of Steve Graham
Sent: Friday, August 01, 2003 9:18 AM
To: Liu, Kevin
Cc: 'w3c-ws-desc@w3.org'
Subject: RE: small updates/rewordings to the report from the Attributes
Ta sk Force

Kevin:

Yes, the access (read, write, read-write) is a property of the
attribute.
An attribute that has no means to change (eg something that comes from
an
underlying resource that cannot be directly updated by anything but the
resource itself), would have a read-only access.

Note, the notion of how the actual security level access is expressed
can
allow further user-level restrictions on the fundamental property of the
attribute.

sgg

++++++++

From: "Liu, Kevin" <kevin.liu@sap.co>
To: Steve Graham/Raleigh/IBM@IBMUS, "'w3c-ws-desc@w3.org'"
<w3c-ws-desc@w3.org>

Steve,

In the following,

    <attribute
        element="xs:QName"
        access= "read" | "write" | "read-write"? >
      <documentation />
    </attribute>*

Are you suggest that the access right is same for all requestors?

Best Regards,
Kevin


-----Original Message-----
From: Steve Graham [mailto:sggraham@us.ibm.com]
Sent: Thursday, July 31, 2003 10:29 AM
To: w3c-ws-desc@w3.org
Subject: small updates/rewordings to the report from the Attributes Task
Force





(See attached file: Report from the Attributes Task
Force.preliminary.3.htm)

++++++++
Steve Graham
sggraham@us.ibm.com
(919)254-0615 (T/L 444)
STSM, On Demand Architecture
++++++++





Received on Wednesday, 3 September 2003 15:06:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:26 GMT