There were in the 3.0.1 version - things like isReplacedBy, and so
forth. Using all lower case means that the word boundaries are no longer
distinguished: derivedfrom, entitykeyvalues and isreplacedby - making
them harder to read.
The canonicalisation algorithm already converts them to lowercase - why
would we need to do it to the keys?
I'm not in favour of anything that makes them harder to read, and that's
the effect of rendering them in all lower case. I wouldn't mind so much
if we reinstated the word boundaries using, for example, underscores;
something like: derived_from, entity_key_values, and is_replaced_by,
would be OK, but that changes the derived V2 keys. The capitalisation, on the
other hand, doesn't change the derived keys, which is one of the reasons I
Still, I'd prefer that we had consistency. Having some in mixed case, and
some in all lowercase, is bad.
From: Von Riegen,
Sent: Fri 11-Jun-04 20:23
To: Rogers, Tony; email@example.com
Subject: RE: [uddi-spec] Typos?
believe that we decided to convert all keys to lower case characters,
probably because of canonicalization. Are there any upper case characters
left in UDDI keys?
I just happened to notice that the UDDI v3 keys for:
are all lower-case,
which is inconsistent with the other canonical tModel keys. Should they
While I'm at it, there's a more serious question:
should probably be:
to be consistent with
But I suspect we won't be too keen on making that change because it
breaks things. Changing the case of derivedFrom and entityKeyValues
shouldn't break things because case isn't significant in comparing UDDI
keys - it won't even change the derived V2 keys, because they must be
mapped to lowercase before being digested.