[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [uddi-spec] Removal of Section 2.3 keyName Changes - adding the capability of making keyName significant
It is proposed that a new find qualifier keyNameSignificant be added to control the significance of keyName in queries. In keyNameSignificant mode all keyName attributes specified in keyedReference elements of a query would be treated as significant for the purpose of matching.
V3 ignores keyName in searches for all practical purposes, except when the corresponding keyedReference’s tModelKey refers to general_keywords category system, in which case keyName is required and is significant in all contexts.keyNameSignificant is not active by default, consistent with V3 behavior.
2.3 keyName ChangesFurther, it is proposed that keyName become a significant query parameter. V3 ignores keyName in searches for all practical purposes, except when the corresponding keyedReference’s tModelKey refers to general_keywords category system, in which case keyName is required and is significant in all contexts. Making keyName significant in all searches in which it is specified would make keyName matching behavior consistent across the general case and the general_keywords case, taking away the (“magical”) special treatment of general_keywords.
Could the TC provide supporting arguments in favour or not of this requirement. As it stands, it's been removed from Prop 20 [1].
Luc
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]