Changes between Version 4 and Version 5 of ComponentVersioning


Ignore:
Timestamp:
04/10/12 11:59:59 (12 years ago)
Author:
twagoo
Comment:

client information

Legend:

Unmodified
Added
Removed
Modified
  • ComponentVersioning

    v4 v5  
    3030=== Client information ===
    3131
    32 Because most clients will consume the XSD transformation of components, the deprecation/versioning information will have to be represented in these profile schemata. It can be provided within an xs:appinfo element. This information can be taken from two proposed new ''optional'' header elements in the component specification: '''Deprecated''' and '''!SuccessorsList'''.
     32Because most clients will consume the XSD transformation of components, the deprecation/versioning information will have to be represented in these profile schemata. It can be provided within an xs:appinfo element. This information can be taken from two proposed new ''optional'' header elements in the component specification: '''Deprecated''' and '''!SuccessorsList'''. The contents of these will come from the database.
    3333
    3434Example: