Claus,
I understand that it is not explicitly specified anywhere in the spec, but
my personal interpretation of any literal string is that it is
case-sensitive, unless explicitly specified otherwise. My feeling is that
others operate similarly, although, certainly, alternative interpretation is
possible.
Specification text always maintains proper case when listing find
qualifiers' short names. I wonder whether this implies that the authors
intended for the find qualifiers to be case-sensitive.
You skipped the "Alternatives Considered (optional)" section, so we have no
way of knowing why you settled on the case-insensitive approach. Is it
because the alternative is more restrictive than a spec reader's potential
assumption?
Daniel
> -----Original Message-----
> From: [mailto:]
> Sent: Thursday, July 17, 2003 12:37 PM
> To:
> Subject: [uddi-spec] Groups -
> uddi-spec-tc-cr042-caseFoldFindQualifiers-20030717.doc uploaded
>
>
> The document
> uddi-spec-tc-cr042-caseFoldFindQualifiers-20030717.doc has
> been submitted by Claus von Riegen ()
> to the UDDI Specification TC document repository.
>
> Document Description:
> Please review this new CR. I'd like to put it on next week's agenda.
>
>
>
> Thanks,
>
> Claus
>
> Download Document:
> http://www.oasis-open.org/apps/org/workgroup/uddi-spec/downloa
d.php/2920/uddi-spec-tc-cr042-caseFoldFindQualifiers-20030717.doc
View Document Details:
http://www.oasis-open.org/apps/org/workgroup/uddi-spec/document.php?document_id=2920
PLEASE NOTE: If the above links do not work for you, your email application
may be breaking the link into two pieces. You may be able to copy and paste
the entire link address into the address field of your web browser.
-OASIS Open Administration
You may leave a Technical Committee at any time by visiting
http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members/leave_workgro
up.php
