FpML-AWG intra-document references

All,

I think we have some problems regarding the use of references within an FpML document (href). See the following issues:

All of these issues have the same common problems:

In some cases the use of href is not properly documented so it is impossible to know where the href is pointing at.
In other cases, the href may point to multiple types (i.e. assetReference). I assume this is a problem for any OO tool.

See comment from Matthew Rawlings on issue 210: If this can point to any type of leg then you need to implement issue 54 to define a Leg type. From a modelling point of view a reference should only point to a single specific type. For this that type is "Leg". The alternative - having a reference point to multiple types is how things used to be before OO in the early '80s.

Another problem is that we have different types to model references. We have complex types such as PartyReference, PricingInputReference,…All these types come from an abstract Reference type containing and href attribute of type IDREF. However, we have also href attributes contained within other complex types that contain other elements. In these latter case, we should probably have simple types defined as a restriction of xsd:IDREF to clarify where the href attribute is pointing at.

<xsd:simpleType name="SimplePricingStructureReference">

<xsd:annotation>

<xsd:documentation xml:lang="en">Reference to a pricing structure or any derived components (i.e. yield curve).</xsd:documentation>

</xsd:annotation>

<xsd:restriction base="xsd:IDREF"/>

</xsd:simpleType>

· Finally, we are missing validation rules to enforce that the references are pointing at the right place.

I think we should clarify the use of references. They are useful but guidelines on the Architecture Spec should be more restrictive on how to use them.

Let me know your thoughts.

Kind Regards,

-Marc

+13472846531