Target Namespace | http://cufxstandards.com/v5/Investment.xsd |
---|---|
Version | 5.0.Revision |
Element and Attribute Namespaces |
|
Schema Composition |
|
Prefix | Namespace |
---|---|
Default namespace | http://cufxstandards.com/v5/Investment.xsd |
xml | http://www.w3.org/XML/1998/namespace |
xs | http://www.w3.org/2001/XMLSchema |
common | http://cufxstandards.com/v5/Common.xsd |
account | http://cufxstandards.com/v5/Account.xsd |
relationship | http://cufxstandards.com/v5/Relationship.xsd |
contact | http://cufxstandards.com/v5/Contact.xsd |
investmentHolding | http://cufxstandards.com/v5/InvestmentHolding.xsd |
Name | InvestmentList |
---|---|
Type | InvestmentList |
Nillable | no |
Abstract | no |
Documentation | Top level investment list collection element. |
Name | Investment |
---|---|
Abstract | no |
Documentation | Details relating to an investment. |
Name | InvestmentList |
---|---|
Abstract | no |
Name | InvestmentParty |
---|---|
Abstract | no |
Documentation | This object points to the party and how it relates to the Investment. |
Name | InvestmentPartyIdList |
---|---|
Abstract | no |
Documentation | The list of investment party ID’s that should have their associated investment / party id cross references either returned or affected by a read, update or delete account request. |
Name | InvestmentPartyList |
---|---|
Abstract | no |
Documentation | A collection of party ID’s that uniquely identify each party associated to this investment and additional fields on how the party relates to the Investment. This list is in addition to the relationship parties if available. |
Name | InvestmentPartyRelationshipType |
---|---|
Abstract | no |
Documentation | The investment party type is the textual representation of what the party record represents to this investment, such as primary, co-borrower, beneficiary or some other type of relationship. This value may be visible to the user and must be human-readable. If the same party exists at the relationship level, the account level relationship type overrides this relationship. Intended choice - Due to cross language serialization issues the choice construct has been removed. It is the responsibility of the implementer to add programmatic logic for this complex type to detect, handle and or error when population of more than one element is present. |