374: Architecture rule of href must point to a single type
Add a rule to the architecture for 5.0 that states that each href must point to a single type. Leave the modelling of the implementation to the Product and Process groups.
Add a rule to the architecture for 5.0 that states that each href must point to a single type. Leave the modelling of the implementation to the Product and Process groups.
Please add an FpML 6.0 WD1 to the Product Version for us to lodge items that won’t make it into FpML 5.0.
Update the AWG membership list on the website. John Weir has moved on within GS. http://www.fpml.org/wgroup/awg/awg.html
The old bugs of floating comments and redundant includes have been reintroduced. See below for examples. As it is the same person doing this each time, please can you sort him out. A type defining a content model that includes valuation (pricing and risk) data without expressing any processing intention. The FpML element forms the … Continued
The capitalization of “FpML” breaks FpML’s own architecture guidelines. It is also giving tools a hiccough as many tools parse this camel case into “Fp M L”. A good example of this is EMF’s editor.
Cannot instantiate Convertible Bond because underlyingEquity IS-A UnderlyingAsset which is abstract, whereas in FpML-4-2 this has been resolved because underlyingEquity IS-A EquityAsset
Since the A2A messages were deprecated, there have been requests to have trade execution messages with appropriate content model.
https://bugs.eclipse.org/bugs/votes.cgi?action=show_bug&bug_id=185357
“Taken from the schemas that the recipient validated against.” – this is impossible to know before a message is validated. Is this just a mistake in the definition? Indicate which version of the FpML Schema an FpML message adheres to. The message creator can send the build number of the schema on which they built … Continued
Rename StandardAttributes.atts. What are these attributes standard to? Also add a definition.