81: Turbo XML TIBCO (2.4.1)

– The presence of two or more elements with the same name within a xsd:choice or xsd:group structures is not supported. The issue doesn’t allow to fix non-deterministic content models within a xsd:choice. – anyAttribute is not supported in AttributeGroup. – Type restriction does not properly generate diagrams or validate. – Optional occurrences of xsd:group … Continued

79: Castor (0.9.5-stable)

– complex Content restriction is not supported – Substitution groups are unsupported – Elements and attributes with the same names are not supported – xsd:any is not supported

71: Proposal to add new value to the TimeTypeEnum

SwapsWire would like to propose the addition of a value to the TimeTypeEnum enumeration in the FpML 4.1 Trial Recommendation for use in equity derivatives. This need has been identified as a result of using FpML to model trades documented under the European interdealer equity option master confirmation. This enumeration is used in the equityOptionTransactionSupplementequityExercise\equityExpirationTimeType … Continued

35: Collateral Type in FpML 4.1 LCWD

The collateral definitions in FpML 4.1 LCWD, specifically the “PaymentDetail”, allow either an amount or a percentage to be specified. The Data Standards Working Group would like the ability to specify both. Is it possible to change the definition to allow both to be specified?

67: MessageRejected

Shouldn’t the MessageRejected be defined as a ResponseMessage? The TradeAffirmed message is defined as a ResponseMessage, while the MessageRejected is defined as a NotificationMessage. In a messaging model I think any Message can be Rejected, but the Rejection will always be a response to another message, e.g. TradeAffirmation. In that case one would like to … Continued