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
My question is, referring to SBE 2.x, if is possible to use the <ref> tag to link to a composite type that was just defined as a nested composite.
I try to explain it with an example.
Imagine that I have this:
Technically the XSD of version 2.x allows this. So is this correct? Could I use a <ref> tag in this way where the composite "priceType" is referred despite is nested definition?
I think that however is desiderable and maybe better to have this solution, right?:
Ok. Could be useful, I think, to refer a nested composite using "." to concatenate the nested composite. In this way I can write longPrice.priceTypeRef
For example, referring to my first example I could write:
This could be an idea to avoid ambiguous interpretation, even if I prefer my second example above where there is not a referring to a nested composite.
My question is, referring to SBE 2.x, if is possible to use the
<ref>
tag to link to a composite type that was just defined as a nested composite.I try to explain it with an example.
Imagine that I have this:
Technically the XSD of version 2.x allows this. So is this correct? Could I use a
<ref>
tag in this way where the composite "priceType" is referred despite is nested definition?I think that however is desiderable and maybe better to have this solution, right?:
The text was updated successfully, but these errors were encountered: