Should documentation be [can’t] instead of [can] ? That is, you use an account reference here when you _can’t_ distinguish which account to use from the party reference alone, such as an inter-book trade.
I’d like to have the schema published for each view, * merged into one file * stripped of comments (which should be for devs, not users) * including annotation/documentation (which is for users) * sorted by kind, then name, with global elements first. Benefits: * Easier to find item in a single schema with documentation … Continued
The FpML specification is silent on what can be inferred from list of Identifiers. Please add to the FpML specification a clear definition. The specific problem experienced is an external application conveying mappings between Identifiers based on appearing in the same list of PartiesAndAccounts.model/party/partyId, and also for PartiesAndAccounts.model/account/@id. The problem occurs when downstream apps try … Continued
In reporting/securities/secrpt-ex01-activity-report.xml a block of text (containing trade properties) has been included after the root element. Possibly a comment was intended. XXX00123 ABCDUS33 HEDGUS33 2004-08-02T15:38:00Z 2004-06-02 BondTrading 2004-06-01T21:23:00 2004-06-02T21:47:00 BOND-20040802001 2004-06-02T08:01:23 2004-06-02 ExampleCUSIP1 JPY 0.014 2011-03-20 JPY 10000000000 99.7 CleanGrossCurrentMarketPrice 101.25 DirtyGrossCurrentMarketPrice 2004-03-20 2004-06-20 false ABCD Securities Inc. HEGDUS33 HedgeCo Capital L.L.C. XXX00123 ABCDUS33 HEDGUS33 … Continued
In fpml-business-rules-5-5.xsd the scheme URI attribute for event types should not start with a capital letter ‘E’.
Annotation on element PartyTradeInformation/clearingStatus is inconsistent with the default coding scheme for its type. Element clearingStatus [ClearingStatusValue] is annotated in schema (fpml-doc-5-3.xsd) as follows: Describes the status with respect to clearing (e.g. Submitted, Pending, Cleared, RejectedForClearing, etc.) However, with the exception of “Pending”, the listed values are not contained in the default coding scheme http://www.fpml.org/coding-scheme/clearing-status … Continued
In the following examples the product needs to be updated to be consistent with the trade date. (A value date 9 years prior to the trade date triggers fx-39).
The definitions needed to support these examples are not in the 5-5-7 REC schema. They should be removed from the distributed example set.
There is an ‘i’ missing in element name ‘requestClearingEligibilty’ The type name is correct, the element is not. This is one of the reasons the example fpml5-5confirmationbusiness-processesclearingmsg-ex100-request-clearing-eligibility.xml fails validation.
There’s a broken link in FpML specification Archive. In FpML 5.1 Recommendation – November 22, 2011 spec, the Download the Master-Schema and Key Generate-scripts (.ZIP) is missing in ther Server. This is the page: http://www.fpml.org/spec/fpml-5-1-8-rec-2/ , and here is the broken link: http://www.fpml.org/spec/fpml-5-1-8-rec-2/xml/fpml-5-1-8-rec-2-master-schema-and-key-gen-scripts.zip