W3C home > Mailing lists > Public > www-ws-desc@w3.org > February 2004

Re: Proposed resolution to issue 143

From: Bijan Parsia <bparsia@isr.umd.edu>
Date: Thu, 26 Feb 2004 11:08:19 -0500
Message-Id: <FE7447B2-6875-11D8-9AD6-0003939E0B44@isr.umd.edu>
Cc: "WS-Description WG" <www-ws-desc@w3.org>
To: "Martin Gudgin" <mgudgin@microsoft.com>

On Feb 26, 2004, at 11:01 AM, Martin Gudgin wrote:
[snip]
>>> I note that 3. is already covered by text in section 3.2:
>>>
>>> "The extension specification SHOULD, if necessary, define
>> additional
>>> properties of 2.1.1 The Definitions Component to hold the
>> components
>>> of the referenced type system. It is expected that additional
>>> extensibility attributes for Message Reference and Fault Reference
>>> components will also be defined, along with a mechanism for
>> resolving
>>> the values of those attributes to a particular imported type system
>>> component."
>>
>> Am I wrong in reading that to say that my extensibility
>> attribute owlClass should populate the current {message}
>> component property with URIs which resolve to components in
>> my new {classes} collection property? If so, that seems to
>> contradict things in section 2.4.
>
> No, I'd expect you to add a new property to the message reference
> component. So we should amend the above text to read
>
> "additional properties and extensibility attributes"

I'm fine with this. I just want it to be clear.

Cheers,
Bijan Parsia.
Received on Thursday, 26 February 2004 11:08:20 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:15:02 UTC