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

[owl-s] Re: Data Flow

From: Bijan Parsia <bparsia@isr.umd.edu>
Date: Fri, 10 Oct 2003 07:13:59 -0400
To: www-ws@w3.org
Message-Id: <D877BBC8-FB12-11D7-82AF-0003936A0B26@isr.umd.edu>

On Friday, October 10, 2003, at 12:58 AM, Mark Baker wrote:

> FWIW, using a RESTful approach to composition seems to simplify things
> greatly.

Perhaps, but it really is a non-starter for our next release. (Which is 
in a week or so :))

>  As each resource is a potential data source (via its state),

I fail to see how that distinguishes this approach from any other. All 
process are a potential data source (via its state...*via*? Due do? I 
would have though that it's behavior counted too.)

> this enables composition to be described with containment relations.

I feel that there must be something I'm missing as this seems to be a 
non-sequitur. Or backwards. I don't see that this happens *because* 
each resource is a data source (*potential* one, no less).
[snip]

It seems to me you have a composition strategy ("containment 
relations") which may indeed be simpler wrt t dataflow (although, 
there's lots of simpler dataflow than what we're doing, but we're also 
trying to represent it more or less explicitly in enough detail to use 
a certain sort of reasoner about it...that's a slightly different task).

Cheers,
Bijan Parsia.
Received on Friday, 10 October 2003 07:17:38 GMT

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