The FpML Issues Tracker is designed to facilitate public interaction in the standard.
By registering to the Issue Tracker you will be able to submit corrections and comments, generate reports, and view the complete issues archive for FpML.


Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0000298 [FpML] Schema major always 2007-02-07 15:27 2007-12-07 09:08
Reporter matthew View Status public  
Assigned To benjlis
Priority normal Resolution open  
Status assigned Target Version 5.0 First Working Draft 2007-08-10 (build 1) Product Version 4.2 Trial Recommendation 2006-12-15
Summary 0000298: BrokerConfirmation is weakly defined.
Description The type BrokerConfirmation is weakly defined:

1. The element has one mandatory child element. What data does this element convey that its children don't? Can it be flattened?
2. The definition is rhetorical. It needs more flesh.
3. brokerConfirmationType is a type - the word type is redundant and should be removed.

    <xsd:complexType name="BrokerConfirmation">
        <xsd:annotation>
            <xsd:documentation xml:lang="en">An entity for details on the broker confirm.</xsd:documentation>
        </xsd:annotation>
        <xsd:sequence>
            <xsd:element name="brokerConfirmationType" type="BrokerConfirmationType">
                <xsd:annotation>
                    <xsd:documentation xml:lang="en">The type of broker confirmation executed between the parties.</xsd:documentation>
                </xsd:annotation>
            </xsd:element>
        </xsd:sequence>
    </xsd:complexType
Additional Information
Tags No tags attached.
XML Tool Type
Attached Files

- Relationships
related to 0000286closedbenjlis BrokerConfirmationType - wrong name, no documentation 

-  Notes
(0000381)
apparry (developer)
2007-03-07 11:58

This is a confirmation message sent from the executing broker to the parties to the execution

The model appears wrong, it is both weakly defined, and incorrectly located

JPM supports this ( AJ, AP, MR, HMcA )
(0000956)
mgratacos (administrator)
2007-11-21 14:59

CDWG: participants (DTCC and T-Zero) think that it's not worth doing these changes.
(0000957)
mgratacos (administrator)
2007-11-21 15:01

There are some architectural about naming and containers that should be tackled by the Modelling Task Force.
(0000958)
mgratacos (administrator)
2007-11-27 17:13

Suggestion from Ben: Identifies the market sector in which the trade has been arranged.
(0000981)
mgratacos (administrator)
2007-12-07 09:08

Documentation of the complex type has been updated in the 4.3 (4.3 branch) and 4.4 (trunk).

- Issue History
Date Modified Username Field Change
2007-02-07 15:27 matthew New Issue
2007-03-07 11:58 apparry Note Added: 0000381
2007-04-04 12:18 matthew Assigned To => benjlis
2007-04-04 12:18 matthew Status new => assigned
2007-04-04 12:18 matthew Target Version => 5.0 (Date of publication not available yet)
2007-11-21 14:59 mgratacos Note Added: 0000956
2007-11-21 15:01 mgratacos Note Added: 0000957
2007-11-21 15:02 mgratacos Relationship added related to 0000286
2007-11-27 17:13 mgratacos Note Added: 0000958
2007-12-07 09:08 mgratacos Note Added: 0000981