Schema "fpml-clearing-processes-5-6.xsd"
Target Namespace:
http://www.fpml.org/FpML-5/pretrade
Version:
$Revision: 9756 $
Defined Components:
4 global elements, 7 local elements, 3 complexTypes
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
C:\Users\mkoli\FpML Specifications\trunk-new\xml\pretrade\fpml-clearing-processes-5-6.xsd; see XML source
Includes Schema:
fpml-business-events-5-6.xsd [src]
Included in Schema:
fpml-main-5-6.xsd [src]
All Element Summary
clearingEligibility
Type:
ClearingEligibility
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
Used:
never
clearingEligibilityAcknowledgement
Type:
Acknowledgement
Content:
complex, 3 attributes, 9 elements
Defined:
globally; see XML source
Used:
never
clearingEligibilityException
Type:
Exception
Content:
complex, 3 attributes, 7 elements
Defined:
globally; see XML source
Used:
never
clearingRequirements
Type:
ClearingRequirements
Content:
complex, 3 elements
Defined:
locally witnin ClearingEligibility complexType; see XML source
eligibleForClearing
Type:
xsd:boolean
Content:
simple
Defined:
locally witnin ClearingEligibility complexType; see XML source
mandatorilyClearable (in clearingRequirements) Whether the particular trade type in question is required by this regulator to be cleared.
Type:
xsd:boolean
Content:
simple
Defined:
locally witnin ClearingRequirements complexType; see XML source
partyTradeIdentifier (in clearingEligibility)
Type:
PartyTradeIdentifier
Content:
complex, 1 attribute, 11 elements
Defined:
locally witnin ClearingEligibility complexType; see XML source
reason (in clearingRequirements) Indicates a reason supporting why the trade is mandatorily clearable or not.
Type:
Reason
Content:
complex, 5 elements
Defined:
locally witnin ClearingRequirements complexType; see XML source
requestClearingEligibilty
Type:
RequestClearingEligibility
Content:
complex, 3 attributes, 19 elements
Defined:
globally; see XML source
Used:
never
requestingPartyReference (in requestClearingEligibilty)
Type:
PartyReference
Content:
empty, 1 attribute
Defined:
locally witnin RequestClearingEligibility complexType; see XML source
supervisoryBody (in clearingRequirements) The regulator or other supervisory body to which the clearing requirements apply.
Type:
SupervisoryBody
Content:
simple, 1 attribute
Defined:
locally witnin ClearingRequirements complexType; see XML source
Complex Type Summary
ClearingEligibility
Content:
complex, 3 attributes, 20 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
ClearingRequirements
Content:
complex, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
RequestClearingEligibility
Content:
complex, 3 attributes, 19 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
XML Source
<?xml version="1.0" encoding="utf-8"?>
<!--
== Copyright (c) 2002-2013 All rights reserved.
== Financial Products Markup Language is subject to the FpML public license.
== A copy of this license is available at http://www.fpml.org/license/license.html
-->
<xsd:schema attributeFormDefault="unqualified" ecore:documentRoot="FpML" ecore:nsPrefix="pre" ecore:package="org.fpml.pretrade" elementFormDefault="qualified" targetNamespace="http://www.fpml.org/FpML-5/pretrade" version="$Revision: 9756 $" xmlns="http://www.fpml.org/FpML-5/pretrade" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore" xmlns:fpml-annotation="http://www.fpml.org/annotation" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:include schemaLocation="fpml-business-events-5-6.xsd"/>
<!-- clearing eligibility -->
<xsd:complexType name="RequestClearingEligibility">
<xsd:complexContent>
<xsd:extension base="CorrectableRequestMessage">
<xsd:sequence>
<xsd:element minOccurs="0" name="requestingPartyReference" type="PartyReference"/>
<xsd:group ref="Events.model"/>
<xsd:group ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ClearingEligibility">
<xsd:complexContent>
<xsd:extension base="ResponseMessage">
<xsd:sequence>
<xsd:choice minOccurs="0">
<xsd:group ref="Events.model"/>
<xsd:element name="partyTradeIdentifier" type="PartyTradeIdentifier"/>
</xsd:choice>
<xsd:element minOccurs="0" name="eligibleForClearing" type="xsd:boolean"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="clearingRequirements" type="ClearingRequirements"/>
<xsd:group ref="PartiesAndAccounts.model"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="ClearingRequirements">
<xsd:sequence>
<xsd:element minOccurs="0" name="supervisoryBody" type="SupervisoryBody">
<xsd:annotation>
<xsd:documentation xml:lang="en">
The regulator or other supervisory body to which the clearing requirements apply.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="mandatorilyClearable" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Whether the particular trade type in question is required by this regulator to be cleared.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="reason" type="Reason">
<xsd:annotation>
<xsd:documentation xml:lang="en">
Indicates a reason supporting why the trade is mandatorily clearable or not.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<!-- ***************************************************************** -->
<!-- Request Limit Check / Messages -->
<!-- ***************************************************************** -->
<xsd:element name="requestClearingEligibilty" type="RequestClearingEligibility"/>
<xsd:element name="clearingEligibility" type="ClearingEligibility"/>
<xsd:element name="clearingEligibilityException" type="Exception"/>
<xsd:element name="clearingEligibilityAcknowledgement" type="Acknowledgement"/>
<!-- Other existing messages used: serviceNotification -->
</xsd:schema>
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.