restricting keyNames

[Richard Jacob <richard.jacob@de.ibm.com>]

I wanted to follow up on our restring keyNames discussion last thursday.

Currently we restrict some keyValues used in keyedReferences/categoryBags
to certain values.
One example is our WSRP Service Type tModel where the keyValue is restriced
to either "Producer" or "Portlet".
The question came up whether we should also explicitly restrict the
keyNames, too.
In this example the keyName would be "WSRP Service Type".
I had a discussion with John again about whether or not to restrict them.

The view we had on the keyName is correct. Currently the keyName can be
viewed as a description of the keyedReference used in a categoryBag.
This might improve readability of the UDDI structures.
However the keyName is never used for searches or any other purposes.
Furthermore there is no possibility to restrict the keyValue inside a
registry like it could be done in private registries or for the Producer
Service Reference in UDDI V3.

Therefor it's more a spec language and openness question here.
Does somebody break interoperability if he doesn't publish the keyName like
we define it in the tech note?
I think the answer here is no, since it's never used.

I agree that for convenience all publisher should use our proposed value in
the tech note.
Therefor for me it seems to be a SHOULD in spec terms here.

This is already contained in the draft-06 document (5.2.1 and 5.3.1).
Do you think this is sufficient?
Is so I would propose to leave it this way.

Mit freundlichen Gruessen / best regards,

        Richard Jacob
______________________________________________________
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development
WSRP Standardization Technical Lead
Phone: ++49 7031 16-3469  -  Fax: ++49 7031 16-4888
Email: mailto:richard.jacob@de.ibm.com