-----Original Message-----
From: Andrew Hately
[mailto:hately@us.ibm.com]
Sent: 02 October 2003 15:52
To: John Colgrave
Cc: uddi-spec@lists.oasis-open.org
Subject: RE: [uddi-spec]
elementFormDefault in uddi_v3policy.xsd
>The
question I was asking was whether unqualified was the correct value for
>elementFormDefault in the policy schema as the
other schemas use qualified.
I
believe the policy schema is written correctly for
elementFormDefault="unqualified" in it's present form. The
difference is not intentional and is likely due to the schema tooling I was
using at the time.
For
consistency, there is no harm in changing the default and updating the
references to the types to be qualified with a prefix inside the schema file.
Andrew
Hately
IBM Austin
UDDI Development, Emerging Technologies
Lotus Notes: Andrew Hately/Austin/IBM@IBMUS
Internet: hately@us.ibm.com
(512) 838-2866, t/l 678-2866
"John Colgrave"
<colgrave@hursley.ibm.com>
10/02/2003 02:27 AM
|
To
|
"'Max Voskob'"
<max.voskob@paradise.net.nz>
|
cc
|
"'UDDI Spec TC'"
<uddi-spec@lists.oasis-open.org>
|
Subject
|
RE: [uddi-spec] elementFormDefault in
uddi_v3policy.xsd
|
|
Max,
The approach of removing the explicit
specification of values that are the
default value was agreed during the last call.
If particular parsers do not
handle defaults correctly then they should be
fixed, and people can add the
value explicitly in the meantime if they have to.
I think the schemas we
produce should be as clear and concise as we can
make them. I suspect that,
for example, if the schemas did not have these
attributes specified unless
they really needed to be, then most of the
questions about the values would
not arise.
I am aware that the default value is unqualified,
I said so in my note.
The question I was asking was whether unqualified
was the correct value for
elementFormDefault in the policy schema as the
other schemas use qualified.
John Colgrave
IBM
> -----Original Message-----
> From: Max Voskob
[mailto:max.voskob@paradise.net.nz]
> Sent: 01 October 2003 21:50
> To: 'UDDI Spec TC'
> Subject: Re: [uddi-spec] elementFormDefault
in uddi_v3policy.xsd
>
> John,
>
> I've come accross a few situations when
parsers did not use the default
> values correctly.
> If we make this change now it may impact on
some existing implementations
> that try to use the new schemas.
> There is no harm in keeping the values
specified even if they specify the
> default values, I think.
>
> The default values for these attributes are
unqualified (see
>
http://www.w3.org/TR/xmlschema-1/#declare-schema)
>
> Cheers,
> Max
>
> ----- Original Message -----
> From: "John Colgrave"
<colgrave@hursley.ibm.com>
> To: "'UDDI Spec TC'"
<uddi-spec@lists.oasis-open.org>
> Sent: Thursday, October 02, 2003 8:30 AM
> Subject: [uddi-spec] elementFormDefault in
uddi_v3policy.xsd
>
>
> I am working my way through the changes to
the 3.0.1 schemas and WSDL, as
> discussed in the last call. One of the
changes I suggested was to remove
> the use of attributeFormDefault and
elementFormDefault when the default
> value was specified. In looking through
the schemas for such occurrences,
> I
> noticed that in uddi_v3policy.xsd the
elementFormDefault has a value of
> unqualified, which is the default value, but
I am not sure that it is the
> correct value for elementFormDefault as that
is specified as qualified in
> the other schemas.
>
> Before I remove this attribute from this schema,
can someone confirm that
> unqualified is the correct value for this
schema?
>
> John Colgrave
> IBM
>
>
>
>
> To unsubscribe from this mailing list (and be
removed from the roster of
> the
> OASIS TC), go to
> http://www.oasis-open.org/apps/org/workgroup/uddi-
> spec/members/leave_workgroup.php.
>
>
>
> To unsubscribe from this mailing list (and be
removed from the roster of
> the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/uddi-
> spec/members/leave_workgroup.php.
To unsubscribe from this mailing list (and be
removed from the roster of the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members/leave_workgroup.php.