OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm-ra message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [soa-rm-ra] quick thought on versioning and description

Title: Re: [soa-rm-ra] quick thought on versioning and description
I would say yes.  While the myth of late binding has sort of been debunked, there are certain situations where auditable events updating a services description could be subscribed to by consumers and changes could automatically happen.  Such instances would probably be limited to minor technical reconfigurations rather than wholesale changes in data models, yet we should definitely consider it a core function.  Many people whining about service management talk about this but there is no clear convention on  major version/minor version upgrade or what scheme would be used to denote such.


On 3/8/07 5:59 AM, "Ken Laskey" <klaskey@mitre.org> wrote:

Would it make sense to add a change log to description where the service provider would list changes that we decide do not constitute the need to update the service version?  Would the version number of the service contain an extra field (thinking of this as an extension to Michael's paper) that indicated a log change but not really anything else?

Not sure where I'd go with this but wanted to capture the thought before it disappeared.


Ken Laskey
MITRE Corporation, M/S H305     phone:  703-983-7934
7515 Colshire Drive                        fax:        703-983-1379
McLean VA 22102-7508


Sr. Technical Evangelist - Adobe Systems, Inc.           *
Chair - OASIS SOA Reference Model Technical Committee    *
Blog: http://technoracle.blogspot.com                    *
Music: http://www.mix2r.com/audio/by/artist/duane_nickull*

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]