The problem with a single indicator is that we cannot
provide 1:M indication - a change in the log may be irrelevant to several
consumers.
If the changes are under the agreement (contract), the
consumer should not care about them, right?
We can recommend, I think, having an archive of the
service description versions and the changes in the description might be
viewed from there.
I still think that a rule-based version control
(does not matter how many version positions the implementation prefers) is the
safe way of addressing multi-version compatibility.
Thank you,
- Michael
Fidelity Investments - Web Delivery
Phone: +44-173-783-6038
E-mail:
Web: http://www.fidelity.co.uk/
Important: Fidelity Investments International, Fidelity Investment Services
Limited, Fidelity Pensions Management and Financial Administration Services
Limited (a Fidelity Group company) are all authorised and regulated in the UK by
the Financial Services Authority and have their registered offices at Oakhill
House, 130 Tonbridge Road, Hildenborough, Tonbridge, Kent TN11 9DZ. Tel 01732
361144. Fidelity only gives information on products and does not give investment
advice to private clients based on individual circumstances. Any comments or
statements made are not necessarily those of Fidelity. The information
transmitted is intended only for the person or entity to which it is addressed
and may contain confidential and/or privileged material. If you received this in
error, please contact the sender and delete the material from any computer. All
e-mails sent from or to Fidelity may be subject to our monitoring procedures.
Direct link to Fidelity’s website -
http://www.fidelity-international.com/world/index.html
From: Ken Laskey [mailto:]
Sent: 08 March 2007 13:59
To:
Subject: [soa-rm-ra] quick thought on
versioning and description
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
------------------------------------------------------------------------------------------
Ken Laskey
MITRE Corporation, M/S H305
phone: 703-983-7934
7515 Colshire Drive
fax:
703-983-1379
McLean VA 22102-7508
