Sure it can be a string.
-----Original Message-----
From: Nick Butler
[mailto:nickb@uk.ibm.com]
Sent: Tue 11/16/2004 7:43 AM
To: Sedukhin, Igor S
Cc: wsdm@lists.oasis-open.org
Subject: Re: [wsdm] please fix status capability in
MUWS...
Igor,
I take your point about not using QNames in this
case, but I am not sure I
agree with your solution, as OperationalStatus is
not an open ended value.
OperationalStatus can take one of only the four
values that are defined in
the MUWS spec. Is there any reason why
OperationalStatus canot be a simple
string, with the four enumerated string
values "Available",
"Partiallyavailable", "Unavailable" and
"Unknown"?
Nick Butler
Autonomic Computing
IBM Hursley
x248081, +44 (0) 1962 818081
"Sedukhin, Igor S"
<Igor.Sedukhin@ca.com> wrote on 16/11/2004 03:29:28:
> It
should be
>
>
<OperationalStatus>{any}</OperationalStatus>
>
>
instead of
<OperationalStatus>xs:QName</OperationalStatus>
>
>
QNames cannot just hang out there. They have to be declared in
> schema,
WSDL, policy or some other document. Declaring them merely
> in the text
is unheard of so far. I suggest we don't do it.
>
> Therefore
there should be XML element declarations which QNames
> correspond to
the intended status values. e.g.
>
> element with
muws-xs:Available QName corresponds to available status.
>
> --
Igor Sedukhin .. (igor.sedukhin@ca.com)
> -- (631) 342-4325 .. 1 CA
Plaza, Islandia, NY
11749
>