element <calculationAgentBusinessCenter> (local)

Namespace: | http://www.fpml.org/FpML-5/reporting
Type: | BusinessCenter
Content: | simple, 2 attributes
Defined: | locally witnin CalculationAgent.model group in fpml-doc-5-5.xsd; see XML source

Content Model Diagram

XML Representation Summary
<calculationAgentBusinessCenter
businessCenterScheme | = | xsd:anyURI : "http://www.fpml.org/coding-scheme/business-center"
id | = | xsd:ID
| >
Content: | { xsd:normalizedString }
</calculationAgentBusinessCenter>

Simple Content Detail:

MaxLength: | 255

Included in content model of elements (17):

  feeTrade, newTrade, oldTrade (in change), oldTrade (in novation), originalTrade (defined in TradeChangeBase complexType), originalTrade (in optionExercise), resultingTrade, trade (defined in DataDocument complexType), trade (defined in Events.model group), | trade (defined in ImpliedTrade complexType), trade (defined in PositionConstituent complexType), trade (defined in TradeOrInfo.model group), trade (defined in TradeValuationItem complexType), trade (in affectedTransactions), trade (in amendment), trade (in change), trade (in clearingStatusItem)

Annotation
The city in which the office through which ISDA Calculation Agent is acting for purposes of the transaction is located The short-form confirm for a trade that is executed under a Sovereign or Asia Pacific Master Confirmation Agreement ( MCA ), does not need to specify the Calculation Agent. However, the confirm does need to specify the Calculation Agent City. This is due to the fact that the MCA sets the value for Calculation Agent but does not set the value for Calculation Agent City.
XML Source (w/o annotations (1); see within schema source)

<xsd:element minOccurs="0" name="calculationAgentBusinessCenter" type="BusinessCenter"/>

XML schema documentation generated with DocFlex/XML 1.8.6b2 using DocFlex/XML XSDDoc 2.5.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.