ShowParty schema, example, validation rules, validation stylesheet

ShowParty type: ShowParty

ShowParty extends: BusinessObjectDocument
Structure:
Elements:
Name Type Description
DataArea ShowPartyDataArea

Is where the information that the BOD message carries is provided, in this case ShowParty. The information consists of a Verb and one or more Nouns. The verb (Show) indicates the action to be performed on the Noun (Party).

ShowPartyDataArea extends: DataArea
Structure:
Elements:
Name Type Description
Party reference
Show reference

ShowParty Scenario Diagram

Show schema

Show type: Show

The Show verb is used when sending the information about a specific instance of a business document or entity. The Show verb may be used to respond to a Get request or it can be used in a publish scenario, where it pushes information to other applications based on a business event.Although BODs based on this verb do not commonly cause updates to occur, there may be times when the component receiving the Show decides to use the information it receives to update. This is entirely the decision of the receiving software component and is not forbidden.The behavior of the Show verb is quite straight forward with one exception. The Show response to any Get request needs to read the request carefully to ensure the response is returning the requested Data Types.

Show extends: ConfirmableVerb
Structure:

Party schema

Party type: PartyInstitutional

Allows the communication of party information between business applications with in a given integration. These Parties may play different roles witin an integration from Supplier, Customer, to Carrier and many more.

A business entity that plays some role in the transaction, either actively or by reference (active parties in a purchase might be the CustomerParty or the SupplierParty, while Manufacturer would be referenced Party that plays no active role in the transaction). The Party type carries with it all of the identifying and descriptive information about the party. A specific Party's role name is captured in the corresponding element's name, following the so-called "semantically-named element substitution group" design pattern. The instance is named [rolename]Party, as in SupplierParty, CustomerParty, etc. Each is of type Party, or of some derived type. Need to bring more Party elements into PartyBase, once reg testing can be broken for a little while. mdf

Verb Common Files

Verb.xsd schema

AcknowledgableVerb extends: ConfirmableVerb
Structure:
Attributes:
Name Type Usage Description
acknowledge AcknowledgementType

AcknowledgementType restricts: xs:NMTOKEN
Enumerations:
Always
Never
OnChange

ConfirmableVerb extends: Verb
Structure:
Attributes:
Name Type Usage Description
confirm ConfirmType

ConfirmType restricts: xs:NMTOKEN
Enumerations:
Always
Never
OnChange

Expression restricts: xs:string

ExpressionCriteria
Structure:
Elements:
Name Type Description
SelectExpression Expression

Allows the 1-n number of selection expressions for the information to be returned.

Attributes:
Name Type Usage Description
expressionLanguage xs:string optional

RequestVerb extends: ConfirmableVerb
Structure:
Elements:
Name Type Description
ReturnCriteria

Allows the initator of the BOD to indicate the information (down to the field level) that is requested to be returned. The expressionLanguage indicates the expression language being used.

VerbBase.xsd schema

Verb type: Verb

Verb
Structure:

Noun Common Files