You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, orchestra2md always outputs codes in a codeset table separate from a field definition. This follows the Orchestra XML schema. Alternatively, it could output a few valid values directly in the field definition or for a fieldRef within a message or component. See example below. md2orchestra already parses this format. Also, this format would be natural for many users who may not be familiar with the concept of a codeset.
Counterarguments to consider:
How many codes can be listed within a table cell? This works ok for a few, but would be unwieldy for a long list. Markdown table cells do not support internal line breaks; a break starts a new table row.
An advantage of a separate codeset table is it has room for documentation of each code.
Name
Tag
Presence
Values
NoParties
453
PartyID
required
PartyIDSource
PartyRole
required
1=ExecutingFirm 2=BrokerOfCredit
The text was updated successfully, but these errors were encountered:
Currently, orchestra2md always outputs codes in a codeset table separate from a field definition. This follows the Orchestra XML schema. Alternatively, it could output a few valid values directly in the field definition or for a fieldRef within a message or component. See example below. md2orchestra already parses this format. Also, this format would be natural for many users who may not be familiar with the concept of a codeset.
Counterarguments to consider:
The text was updated successfully, but these errors were encountered: