EMF generates invalid XML Schema after mapping and generating this FpML text. the problem is the umlaut. Typ zur Definition der Ausbungsprozesse bei einer amerikanischen Aktienoption. Diese Einheit leitet sich ab vom Typ “SharedAmericanExercise”. https://bugs.eclipse.org/bugs/show_bug.cgi?id=153698
There is something in the FpML schema that is triggering a slower performance than usual from EMF XSD. Creating an XML Schema to eCore Map for FpML is slow. On a variety of typical 2005/6 PCs, with 2Gb RAM this is taking approximately 30 minutes to 90 minutes on average. The creation of the XML … Continued
In the ZIP archive that contains the entire FpML42 spec, look at the HTML / PDF files for the schema documentation. They only contain ‘Global Elements’ and ‘Global Types’ but they ignore model groups, which means that an increasing number of structures are not documented in the PDFs. ( see gen-schema-html.xsl and gen-schema-xml.xsl : they … Continued
The additionalData element, included in the MessageRejected message may report the original FpML message. This content may include new lines, which are not valid with a normalizedString type. AdditionalData should be of type string as it was in FpML 4.0
fpml-shared-4-2.xsd, Row 11, column 76, the t from time is missing A type defining a ime specified in hh:mm:ss format where the second component must be ’00’, e.g. 11am would be represented as 11:00:00.
Altova’s Mapforce does not support xsi:type in elements. This is true up to version 2006, release 3, service pack 1.
Some readme files are “README.txt” and some are “readme.txt”. Please make them all consistent.
The root page of the HTML documentation has a cryptic name. You need to navigate to tr-fpml-4-2-2006-05-08/html/fpml-4-2-intro-frame.html Rather than the catchy “fpml-4-2-intro-frame.html”, please could it be called “index.html” which is a web convention for the main page. It would make life so much easier. Optionally, you could also add a readme conveying this information
The date display format used in Issues Tracker (e.g. Date Submitted, Last Update) is ambiguous. Date/times are displayed in the form “MM-DD-YY hh:mm” – so a date like “05-06-07” has (at least) three possible interpretations depending on the cultural background and locale of the reader. I suggest we adopt the ISO 8601 international standard notation … Continued
I found out that the FpML specs are a bit ambiguous with respect to the definition of country codes and countryScheme. From: http://www.fpml.org/spec/2006/tr-fpml-4-2-2006-05-08/html/fpml-4-2-schemes-frame.html URI: http://www.fpml.org/ext/iso3166 A valid 2 character country code as defined by the ISO standard 3166 – Codes for representation of countries http://www.niso.org/standards/resources/3166.html. It really should be “ISO 3166-1 alpha-2”. ISO 3166 is … Continued