issues
search
FIXTradingCommunity
/
fix-orchestra-spec
Technical specification for FIX Orchestra (machine readable rules of engagement)
Other
25
stars
4
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Mention optional name attribute
#54
kleihan
opened
4 days ago
0
Clarify presence rules for scenario ID/name for references
#53
kleihan
opened
9 months ago
0
Update non-normative section on mapping messages to scenarios
#52
kleihan
opened
9 months ago
0
Sharing of namespace for code sets and datatypes
#51
kleihan
opened
9 months ago
1
ISO 20022 datatype "identifer set" versus Orchestra discriminator fields
#50
kleihan
opened
10 months ago
0
Clarify implicit link between field and code set scenarios
#49
kleihan
opened
10 months ago
2
Update section on union datatypes
#48
kleihan
opened
10 months ago
0
Mark part of datatype mapping text as non-normative
#47
kleihan
opened
10 months ago
0
Update section on relevant DC terms
#46
kleihan
opened
10 months ago
0
Update UML metamodel for repository
#45
kleihan
opened
10 months ago
0
Update section 1.1 on objectives
#44
kleihan
opened
10 months ago
0
Fix incorrect reference
#43
michaelboyles
closed
6 months ago
2
Define entity attribute "changeType" in spec
#42
kleihan
opened
1 year ago
2
Terminology: container versus element tree versus element
#41
kleihan
opened
1 year ago
0
Relationship between field and type
#40
donmendelson
opened
2 years ago
1
Metadata usage guidelines
#39
donmendelson
opened
2 years ago
2
Issue #29 remove redundant reference to base scenario
#38
kleihan
closed
2 years ago
1
Correct reference to supplementary documentation and make it available online
#37
kleihan
closed
2 weeks ago
2
Error in presence attribute
#36
kleihan
closed
2 years ago
2
Sort attribute of codeType should be numeric
#35
kleihan
closed
2 years ago
2
Error in example of conditionally required field
#34
kleihan
closed
2 years ago
0
Datatypes needs extensibility and mapping enhancements
#33
donmendelson
closed
10 months ago
3
Use ISO/IEC 11179 terminology for Concepts
#32
donmendelson
opened
2 years ago
0
Error in example
#31
donmendelson
opened
3 years ago
1
Typo in definition of codesets
#30
kleihan
closed
1 year ago
1
Remove scenario="base" from examples unrelated to scenarios
#29
kleihan
closed
1 year ago
1
Add verbiage for all attributes provided in the XSD file
#28
kleihan
opened
3 years ago
1
Add name back into fieldRef and componentRef elements
#27
jimnup
closed
3 months ago
2
Values of attributes "added" and "updated"
#26
kleihan
closed
3 years ago
1
DRAFT: Supplementary documentation references
#25
kleihan
closed
3 years ago
0
DRAFT: Schema location update
#24
kleihan
closed
3 years ago
0
Time literals
#23
kleihan
closed
4 years ago
7
References to supplementary documentation
#22
kleihan
closed
4 years ago
1
Case sensitivity of names
#21
kleihan
closed
4 years ago
4
Underspecification of timer element
#20
kleihan
closed
4 years ago
1
Examples with non-standard FIX elements
#19
kleihan
closed
4 years ago
1
Use cases for the presence attribute "forbidden"
#18
kleihan
closed
4 years ago
4
Uniqueness of component names
#17
kleihan
closed
4 years ago
3
Document volumes vs business areas
#16
kleihan
closed
4 years ago
1
Role of Extension Packs
#15
kleihan
closed
4 years ago
1
Repository attributes - expressionLanguage
#14
kleihan
closed
4 years ago
3
XML Schema location update
#13
kleihan
closed
4 years ago
3
Size of interface diagram
#12
kleihan
closed
4 years ago
3
FIX Orchestra vs FIX Repository
#11
kleihan
closed
4 years ago
4
Union datatype
#10
donmendelson
closed
2 years ago
1
typo in spec
#9
guillaume-alvarez
closed
5 years ago
0
Schema lacks enum value for mapping to tag value encoding
#8
donmendelson
closed
4 years ago
1
Support XInclude for reusable message and field definitions
#7
donmendelson
closed
4 years ago
0
Change Section element to BusinessArea for ISO 20022 alignment
#6
jimnup
closed
5 years ago
9
Refactoring Abbreviations
#5
jimnup
closed
4 years ago
2
Next