Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "ALF/architecture/ALF Schemas 1"
(→Introduction) |
(→Introduction) |
||
| Line 11: | Line 11: | ||
Some of the features to note are: | Some of the features to note are: | ||
| − | 1. The provision for extension and versioning using nested "Extension" elements. The approach pursued is based primarily on the recommendations of this article, "Extensibility, XML Vocabularies, and XML Schema" by David Orchard[ | + | 1. The provision for extension and versioning using nested "Extension" elements. The approach pursued is based primarily on the recommendations of this article, "Extensibility, XML Vocabularies, and XML Schema" by David Orchard[http://www.xml.com/pub/a/2004/10/27/extend.html] |
2. The refactoring of the BaseEvent to divide it into two parts; the part normally set by the tool raising the event and the part normally set by the alf event manager. The primary motivation for this is to establish a structure of elements that can be passed on to the services of "alf compliant" tools. The needs of this structure correspond to those elements that are normally set by the event manager. | 2. The refactoring of the BaseEvent to divide it into two parts; the part normally set by the tool raising the event and the part normally set by the alf event manager. The primary motivation for this is to establish a structure of elements that can be passed on to the services of "alf compliant" tools. The needs of this structure correspond to those elements that are normally set by the event manager. | ||
Revision as of 20:26, 6 February 2007
Introduction
ALF Event Manager Schemas and WSDL version 1
WARNING: THIS PAGE IS BEING CONSTRUCTED. THE INFORMATION IT CONTAINS IS PRELIMINARY
The proposed version 1 ALF Event schema is presented below.
Some of the features to note are:
1. The provision for extension and versioning using nested "Extension" elements. The approach pursued is based primarily on the recommendations of this article, "Extensibility, XML Vocabularies, and XML Schema" by David Orchard[1]
2. The refactoring of the BaseEvent to divide it into two parts; the part normally set by the tool raising the event and the part normally set by the alf event manager. The primary motivation for this is to establish a structure of elements that can be passed on to the services of "alf compliant" tools. The needs of this structure correspond to those elements that are normally set by the event manager.