Re: issue: modelReference vs. category

Hi Holger, 

this is issue 10 now. [1]

Just to clarify the terminology, I have to note that in WSDL 2 terms, 
a service is an instance of a single interface which can extend multiple
other interfaces. You are practically correct, but the attribute
"interface" on <service> can still only have a single value, which might
have caused confusion. 8-)

Best regards,

Jacek

[1] http://www.w3.org/2002/ws/sawsdl/issues/#x10

On Tue, 2006-04-25 at 16:25 +0200, Holger Lausen wrote:
> Hi,
> 
> I have a question: We are about to extend WSDL with pointers to semantic
> annotation... Why do we make / did WSDL-S make the distinction between
> <modelReference> for operation and <category> for interface?
> 
> Naively I would expect that both WSDL components would be annotated
> equally (i.e. with a pointer to a semantic model), however within the
> section 2.3 "Service Categorization" the term "semantic model" is not
> mentioned. Additionally I think section 2.3 should be named "interface
> categorization", since in fact a service can inherit from multiple
> interfaces.
> 
> I would suggest to use for both WSDL components the same means of
> annotation (i.e. modelReference), alternatively we could think about a
> more complex pointer mechanism like it is done in service category, but
> then I would expect some justification in the document on why the
> structures are different.
> 
> best
>   Holger
> 
>