1289: Deprecate Valuation/@definitionRef
The complexType Valuation has an attribute definitionRef which should be marked as deprecated, because Valuation already has an element valuationScenarioReference which does the same thing.
The complexType Valuation has an attribute definitionRef which should be marked as deprecated, because Valuation already has an element valuationScenarioReference which does the same thing.
The complexType RateReference should be based on the Reference type, to conform with the pattern of other intra-document pointers.
Could please clarify FpML example “2.66 Example 58 – Cross Currency Swap with Lookback Compound computed floating rate”. This example uses an overnight index and includes two sections: Calculation Parameters and Reset Dates . However, in the FpML schema ird-5-12 there is the description of the Calculation Parameters Section which notes that “when the Calculation … Continued
https://www.fpml.org/spec/fpml-arch-3-1-rec-5/html/index2.html#s2.3.3 Attributes SHOULD be associated with either a XML schema built-in type or and FpML defined simple type to allow the parser to validate document instances. Some attributes are missing types. contractTypeScheme creditSeniorityScheme deliveryTypeScheme initialMarginInterestRateTermsScheme linkTypeScheme href fpmlVersion The scheme attributes should have type=”NonEmptyURI”, as per the pattern other schemes. UnderlyerReference/@href should follow the pattern … Continued
XAPWG Thread [FpML-XAPWG] CMS representation (mockup for discussion) – FpML RE: [FpML-XAPWG] CMS representation (mockup for discussion) – FpML Waiting for Harry’s feedback. Thinks reset is being confused with the fixing date. Reset date is usually calculation period end date. Usually the fixing is determined a few days before the calculation period end date. Usually … Continued
FpML Architecture Specification 3.1#s2.3.5 All elements MUST be associated with a globally defined type 5-12 and 5-13-WD-1 have 5 elements which define local anonymous types They should reuse or convert to global named types. //xsd:simpleType[exists(parent::xsd:element)] RegulatoryWithdrawal/ withdrawalReason //xsd:complexType[exists(parent::xsd:element)] DayCount/ currencySpecificDayCount Rollover/ currentContracts, Rollover/ newContracts AdditionalData/ originalMessage
test
Good evening dear FpML experts. Currently working on the code of example 2.18 Example 10 – European Swaption, Physical Settlement, Relative Underlying Effective Date. I need a little clarification regarding tag <dateRelativeTo href=”europeanExercise0″ /> which is nestled inside of <relevantUnderlyingDate> Swaption`s tag structure. I have two assumptions regarding the meaning of this tag: 1) this is simply … Continued
Good afternoon, In the example “2.17 Example 9a – European Swaption, Physical Settlement, Explicit Underlying Effective Date” (see the code extract bellow), it is provided the tag <paymentType>PremiumAmount</paymentType> which do not have domain values and do not say explicitly what premium type can be nestled inside. Is it possible to nestle Swaption`s Spot or Forward premium … Continued
Hi, we would like to request a new business center for Guayaquil, Ecuador. The proposed code would be ECGU. Thanks, Marc