Re: [wsdm][OMod] Updated Mows data model with versioning

[Fred Carter <fred.carter@amberpoint.com>]

[On OMod call, I expressed concern about the knowledge within a 
versioned component of its revision since that wants to know about 
successor, etc.]

Might we improve things by changing the arrow between "versioned 
component" and "revision" labeled "has" to 1) point the other way, and 
2) be labeled "represents".  Then the "version tracking subsystem" is 
separate and pointing into the WSDL stuff, not the other way around -- 
and doesn't require the changing of an old version to make a new one...

Thus quoth Sedukhin, Igor S (~ 04-Nov-03 10:31 AM ~)...

> Brian,
>  
> I don't disagree with the concepts that you were expressing, but 
> according to our earlier discussion 
> (http://lists.oasis-open.org/archives/wsdm/200310/msg00085.html)
> 
>     1. The versioning was to be expressed in a detail diagram, *in
>     addition* to the concepts diagram. Otherwise the concepts diagram
>     becomes cluttered with way too many things. Also today, per core
>     WSDL there is nothing like what was expressed. We have to keep a
>     practical, concrete point of reference.
>      
>     2. The diagram had to express that a "versioned element X is an
>     element X", not the vice versa. In your diagram, for example, it is
>     expressed that a "functional interface" is an "interface version"
>     which is not excatly true, IMO.
> 
> So, I attemted to reformulate your diagram with the above two concerns. 
> The diagram is attached. The words to follow the diagram are as follows.
>  
> "
> The elements of the Web services acrhitecture, expressed in WSDL, could 
> be versioned. For example description, interface, service and endpoint 
> could be defined in their own namespaces (not necessarily the same). The 
> namespace could be used to contain the version. Therefore, those 
> elements, conceptually become veriosned. For example a versioned service 
> is a service that is also a versioned component that has a version 
> attribute.
>  
> Versioned components have revisions that are related to each other via 
> changes that happened between revisions. Each change indicates a 
> predcessor and sucessor (if any) revisions. Each change may aggregate 
> multiple change descriptions. Each change description may be looked at 
> as a document or a separate statement of some sorts (e.g. "new interface 
> was implemented").
> "
> 
> --* **Igor Sedukhin* .. (igor.sedukhin@ca.com)
> --* (631) 342-4325* .. 1 CA Plaza, Islandia, NY 11788
> 
>  
> 
> ------------------------------------------------------------------------
> *From:* Brian Carroll [mailto:Brian.Carroll@merant.com]
> *Sent:* Tuesday, November 04, 2003 10:57 AM
> *To:* wsdm@lists.oasis-open.org; 'Andreas Dharmawan'
> *Subject:* RE: [wsdm][OMod] Updated Mows data model with versioning
> 
> Igor and all,
>  
> Here is an updated slide for the overall MOWS data model that includes 
> versioning.  Sorry for the delay, but I just obtained Visio 2003 yesterday.
>  
> The Change entity relates two Service Versions.  For clarity, I've taken 
> Zulah's comments to heart and renamed the relationships between versions 
> as "predecessor and successor".
>  
> Igor, I will send the updated Visio file to you in a separate e-mail.
>  
> Regards,
> Brian
> 
> Notice: This email transmission and/or the attachments accompanying it 
> may contain confidential information belonging to Merant. The 
> information is only for the use of the intended recipient. If you have 
> received this transmission in error, please notify the sender 
> immediately by reply email, and then destroy all copies of the 
> transmission.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> 
> ------------------------------------------------------------------------
> 
> 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/wsdm/members/leave_workgroup.php.


-- 
Fred Carter / AmberPoint, Inc.

mailto:fred.carter@amberpoint.com
tel:+1.510.433.6525 fax:+1.510.663.6301