[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [soa-rm-ra] Version
Here is why I thought that version was connected to identity:
A resource is a time varying entity that has value to someone (or something)
DN: everything varies with time so it is not unique, therefore why mention it.
A version identifies a particular state of the resource at a particular moment in time (could include space too).
The resource may or may not have any 'awareness' of its versions. In fact, I would argue that most of the time it does not.
DN: this is orthogonal. I think most version changes really represent different states visible outside the service, not necessarily what powers them.
Consider a description of a service. That description will have many aspects to it. It may also identify which version of the service the description pertains to.
Now, consider versioning the description itself. In the case of a description, it is a structure artifact and so it may be possible to 'fit' any version identification of the description into the description itself. But, if the description was designed to a specification that neither enabled versioning nor enabled extensions, then you could not embed version info into the description artifact (straw man I now, but other resources have no space for version info).
DN: I would not consider versioning the description. I think it is simpler if you describe the service and any unique service/version instances.
BTW – here are the minutes – please add any changes before committing. Sorry I had to run earlier.
Meeting Minutes from June 25.docx