FpML Issues Tracker
closed
Minor
Always
Architecture
Admin
andrew
Summary
Currently there are three views defined "Pre-Trade", "Confirmation", and "Reporting". The problem I have is the schema file names clash across three views.
For example fpml-5-0-main.xsd in Confirmation clashes with fpml-5-0-main.xsd in Pre-Trade.
My suggestion is that each schema name is unique. This could be by a choice of: * Unique named generated using annotations on the master schema * Prefixing the view name * Using a directory structure * etc.
Notes:
mgratacos
02/07/08 2:42 pm
AWG 2008-01-24: leave it as it is and wait for implementation feedback on whether this is a problem or not.
matthew
02/08/08 2:24 pm
The issue was raised as feedback following my first implementation. On that basis IMHO it is “implementation feedback”.
andrew
02/08/08 3:03 pm
Owners of other existing implementations have given feed back that distributing the schemas in the current form is not an issue.
To operate reliably no XML processing software should ever use the contents of the ‘schemaLocation’ attribute to identify the correct schema source for validation. This attribute is populated by the document creator and any file path it contains is may not be valid on the document processor’s system.
The link between document and schema should always be determined by a resolution process base on the declared namespace URIs and using a technology such as C#/JAXP’s pre-compiled schema collections or an XML catalog.
All the other implementations use such a process and are therefore able to process documents regardless of the value of ‘schemaLocation’.
mgratacos
02/21/08 2:33 pm
AWG 2008-02-20: The directory structure is already in place.