Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terminology: container versus element tree versus element #41

Open
kleihan opened this issue Feb 22, 2023 · 0 comments
Open

Terminology: container versus element tree versus element #41

kleihan opened this issue Feb 22, 2023 · 0 comments
Assignees
Labels
ERRATA Errors and omissions, inconsistencies

Comments

@kleihan
Copy link
Member

kleihan commented Feb 22, 2023

The v1.0 spec uses all 3 terms and the difference is unclear. This should be made consistent.

Examples:

An internal <codeSet> is a container for <code> elements. 
It is a reference to a `<field>` element within the `<fields>` container.
In the schema, a `<field>` element is contained by parent element `<fields>`.
The `<messages>` element contains any number of child `<message>` elements.
The `<actors>` element tree provides a place to store such external state information.
The `<categories>` element tree is used to associate FIX elements to business areas.
The `<sections>` element tree names higher level business processes. 
@kleihan kleihan added this to the Orchestra v1.1RC1 milestone Feb 22, 2023
@kleihan kleihan added ERRATA Errors and omissions, inconsistencies and removed enhancement labels Aug 21, 2024
@kleihan kleihan self-assigned this Aug 21, 2024
@kleihan kleihan moved this to Backlog in Orchestra v1.1 RC2 Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ERRATA Errors and omissions, inconsistencies
Projects
Status: No status
Development

No branches or pull requests

1 participant