[1] I don't see an usage for Version attribute of Service/Component tag, and
Service tag either. The meta could be a simple set of *simple* attributes,
and be extended by those who want it. By now, these information can be made
optional in the object model, and we go from there.
An interface can go though version changes without necessarily impacting its signature. In effect version on a service captures the semantic and computation contract of the service. In turn, service version information is used when potential candidate component types with versioned service dependencies exposed by a component.
It's rather fine grain - but essential when your dealing with standards based generated interface backed by component implementations that implement a particular semantic and computational version (think CORBA/IIOP, IDL, and PSDL generated content).
Cheers, Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
