RE: [uddi-spec] Groups - uddi-spec-tc-cr083-multiversioning inconsistency-20040809.doc uploaded

Why 
don't I take a stab at revised text after the telecon.

From: John Colgrave [mailto:] 

Sent: Tuesday, August 10, 2004 08:46
To: Luc 
Clement
Cc: ; 

Subject: RE: [uddi-spec] Groups - 
uddi-spec-tc-cr083-multiversioning inconsistency-20040809.doc 
uploaded

Luc, 

By definition, a value set with entity keys as valid 
values is represented by a tModel categorised using the entityKeyValues category 
system.  If you prefer to describe the behaviour in terms of the concrete 
representation then change the section heading to be something about tModels 
categorised using the entityKeyValues category system. 

Regards,

John
--------------------------------------------------
John 
Colgrave
Architect, IBM WebSphere UDDI Registry 

"Luc Clement" <> wrote on 10/08/2004 
16:02:04:

> John, I disagree with the statement "I don't think it is 
necessary 
> to say that the behaviour applies to tModels categorised 
using the 
> entityKeyValues category system as the entire section is 
about value
> sets with entity keys as valid values, and the two things 
are equivalent." 
>   

> This section of the spec simply does not make it 
explicit that this 
> applies to keyedReferences whose tModel is 
categorized using 
> entityKeyValues; one has to imply this from the 
heading and from the
> "See section...". 
>   
> We might argue over 
the text but I definitively think that 
> clarifying this behaviour is 
necessary. 
>   
> Luc 
> 
> 
  
> From: John Colgrave 
[mailto:] 
> Sent: Tuesday, August 10, 2004 
07:49
> To: 
> Cc: 

> Subject: Re: [uddi-spec] Groups - 
uddi-spec-tc-cr083-multiversioning
> inconsistency-20040809.doc 
uploaded

> 
> The sentence you seem 
to have trouble with is English (at least 
> British English, it may not 
be American English).  The meaning of 
> the sentence is (was 
intended to be) "Entity keys when used as 
> keyValue values with value 
sets that use entity keys as valid values
> must be mapped in the same way 
that entity keys are mapped in all 
> other places that they occur." 

> 
> I think the proposed replacement sentence is less accurate. 
 It 
> assumes that a V3 key is supplied, and therefore does not make 
sense
> in the example in the following paragraph. 
> 
> I 
don't think it is necessary to say that the behaviour applies to 
> 
tModels categorised using the entityKeyValues category system as the
> 
entire section is about value sets with entity keys as valid values,
> and 
the two things are equivalent. 
> 
> Regards,
> 
> 
John
> --------------------------------------------------
> John 
Colgrave
> Architect, IBM WebSphere UDDI Registry
> Telephone/FAX: 
+44 (0)1962 816887 
> 
>  wrote on 
10/08/2004 14:52:17:
> 
> > The document 
uddi-spec-tc-cr083-multiversioning 
> > inconsistency-20040809.doc has 
been submitted by Mirek Novotny 
> > () to 
the OASIS UDDI Specification TC 
> > document repository.
> > 

> > Document Description:
> > Conversion to v2 key format of 
keyValues of entityKeyValue-based 
> > keyedReferences
> > 

> > Download Document:  
> > 
http://www.oasis-open.org/apps/org/workgroup/uddi-spec/download.
> > 
php/8642/uddi-spec-tc-cr083-multiversioning%20inconsistency-20040809.doc
> 
> 
> > View Document Details:
> > 
http://www.oasis-open.org/apps/org/workgroup/uddi-spec/document.php?
> 
> document_id=8642
> > 
> > 
> > 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 copyand 
paste
> > the entire link address into the address field of your web 
browser.
> > 
> > 
> > 
> > To unsubscribe 
from this mailing list (and be removed from the 
> > roster of the 
OASIS TC), go to http://www.oasis-open.
> > 
org/apps/org/workgroup/uddi-spec/members/leave_workgroup.php.
> > 

smime.p7s