SyncParty schema, example, validation rules, validation stylesheet

SyncParty type: SyncParty

The purpose of the SyncParty is to facilitate keeping party information synchronized that exists on separate data bases. The SyncParty allows the adding of new party and the modification of previously established parties.

SyncParty extends: BusinessObjectDocument
Structure:
Elements:
Name Type Description
DataArea SyncPartyDataArea

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

SyncPartyDataArea extends: DataArea
Structure:
Elements:
Name Type Description
Party reference
Sync reference

SyncParty Scenario Diagram

Sync schema

Sync type: Sync

The Sync verb is used when the owner of the data is passing or publishing that information or change in information to other software components. This is to be used when the receiver of the SyncBOD does not own the data. This verb is commonly used when mass changes are necessary or when a publish and subscribe mechanism is used in the integration architecture.The purposes of this verb include application integrity and ease of data entry for the business user by enabling a single point of input.

Sync extends: ConfirmableVerb
Structure:
Elements:
Name Type Description
SyncCriteria SyncExpressionCriteria

SyncExpressionCriteria
Structure:
Elements:
Name Type Description
SyncExpression
Attributes:
Name Type Usage Description
action required
expressionLanguage
Enumerations:
Add
Change
Delete
Replace

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