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 "Talk:ALF/architecture/ALF Schemas 001"
(on Additional Changes 1. Combine Detail and Extension to a single xs:any element perhaps called <payload>.) |
|||
| Line 1: | Line 1: | ||
Please comment on this document here | Please comment on this document here | ||
| + | |||
| + | == on Additional Changes 1. Combine Detail and Extension to a single xs:any element perhaps called <payload>. == | ||
| + | |||
| + | - posted for Brian Carroll | ||
| + | The intent of separating the two parts of the payload into the standard part defined by an ALF Vocabulary and tool-specific extension data was to allow for tool substitutability. Any arbitrary tool that understood the ALF Vocabulary-defined portions but not the tool-specific data could still process the standard portion of the payload. Separating the standard ALF Vocabulary-defined portions from the tool extension data make the event more generically process able by tools that simply understand the ALF Vocabulary portion. We need to keep that separation. | ||
Revision as of 14:41, 14 September 2006
Please comment on this document here
on Additional Changes 1. Combine Detail and Extension to a single xs:any element perhaps called <payload>.
- posted for Brian Carroll The intent of separating the two parts of the payload into the standard part defined by an ALF Vocabulary and tool-specific extension data was to allow for tool substitutability. Any arbitrary tool that understood the ALF Vocabulary-defined portions but not the tool-specific data could still process the standard portion of the payload. Separating the standard ALF Vocabulary-defined portions from the tool extension data make the event more generically process able by tools that simply understand the ALF Vocabulary portion. We need to keep that separation.