W3C home > Mailing lists > Public > public-ws-semann@w3.org > June 2006

Re: issue 18: Relation of multiple modelReferences

From: Jacek Kopecky <jacek.kopecky@deri.org>
Date: Tue, 13 Jun 2006 22:19:49 +0200
To: Laurent Henocque <laurent.henocque@gmail.com>
Cc: SAWSDL public list <public-ws-semann@w3.org>
Message-Id: <1150229989.17198.14.camel@localhost>

Hi Laurent, 

I opened issue 21 about making modelReference an element (will soon be
available in the issues list online).

The thing about attributes vs. elements is in extensibility, as you
yourself argue, but I don't see how extending modelReference would be
useful - we don't give modelReference much meaning so there's not much
to be changed by extensions...

That is, unless we decide to couple schemaMapping with modelReference,
but we haven't gone there yet.

Allowing extensibility is, in general, good, but in our case we have an
attribute that really represents a hook for extending WSDL/Schema
components. Any extensibility should be happening at the target of the
modelReference, I'd say.

Best regards,

Jacek

On Tue, 2006-06-13 at 12:07 +0200, Laurent Henocque wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Again, some pragmatic moves:
> 
> I understand that it could be harmful to freeze in marble constructs that would conflict with the average use, in an
> unknown future.
> 
> For that reason, I am ready to accept the idea that model references are not grouped in 'contexts'. It is clear that in
> so doing, we defer any selection of references to uri parsing or distant file querying. I am very unhappy with abusing
> string or uri parsing, and I guess that distant file querying may pose problems as well (availability?). But these are
> not major problems.
> 
> What we need to however, is to prepare for smooth evolution. I hence strongly support lifting modelReferences from
> attributes to elements, as you corrected me:
> 
> <element name="fullName" type="xsd:string">
>      <sawsdl:modelReference>ontology#FullName</sawsdl:modelReference>
>      <sawsdl:modelReference>ontology#FirstName</sawsdl:modelReference>
>      <sawsdl:modelReference>ontology#LastName</sawsdl:modelReference>
> </element>
> 
> In so doing, we would smoothly prepare for evolution or extension by extra attributes, hence allowing to defer choices
> relevant with the relationship between modelReferences.
> 
> Hoping that it will help moving forward.
> 
> Laurent
> 
Received on Tuesday, 13 June 2006 20:19:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:58:45 UTC