OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

uddi-spec message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [uddi-spec] Groups - uddi-spec-tc-cr042-caseFoldFindQualifiers-20030717.doc uploaded

Title: Message
There is no particular reason that's specific to this case, just the general rule of not allowing unnecessary variability in message content to make the payloads easier to process and to eliminate dumb errors.
I am not suggesting that this be one way or another - just trying to figure out the reasoning.  Your response was helpful.
Thank you,
-----Original Message-----
From: Rogers, Tony [mailto:Tony.Rogers@ca.com]
Sent: Thursday, July 17, 2003 3:34 PM
To: Daniel Feygin; claus.von.riegen@sap.com; uddi-spec@lists.oasis-open.org
Subject: RE: [uddi-spec] Groups - uddi-spec-tc-cr042-caseFoldFindQualifiers-20030717.doc uploaded

While this is an interesting suggestion, I don't see it that way.
There is no risk of confusing one find qualifier with another, even if we accept any case. Therefore I see no reason to insist that the qualifiers be provided in any particular case. If a request arrives with a find qualifier of "ORLIKEKEYS" or even "OrLiKeKeYs", then I'm happy to accept that as indicating the intent of the request, even if it doesn't match the case in the spec.
Is there a good reason for these to require matching case?
-----Original Message-----
From: Daniel Feygin [mailto:feygin@unitspace.com]
Sent: Thu 17/07/2003 21:09
To: claus.von.riegen@sap.com; uddi-spec@lists.oasis-open.org
Subject: RE: [uddi-spec] Groups - uddi-spec-tc-cr042-caseFoldFindQualifiers-20030717.doc uploaded


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

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


> -----Original Message-----
> From: claus.von.riegen@sap.com [mailto:claus.von.riegen@sap.com]
> Sent: Thursday, July 17, 2003 12:37 PM
> To: uddi-spec@lists.oasis-open.org
> 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 (claus.von.riegen@sap.com)
> 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

View Document Details:

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

You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members/leave_workgroup.php

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]