26.12.2012 Views

Australian Government Architecture Reference Models Version 3.0

Australian Government Architecture Reference Models Version 3.0

Australian Government Architecture Reference Models Version 3.0

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Term Definition<br />

Exchange Package<br />

An Exchange Package is a description of a specific recurring data exchange<br />

between a Supplier and a Consumer. An Exchange Package contains<br />

information (metadata) relating to the exchange (such as Supplier ID, Consumer<br />

ID, validity period for data, etc.), as well as a reference to the Payload (message<br />

content) for the exchange. An Exchange Package can also be used to define the<br />

result format for a query that is accepted and processed by a Query Point in a<br />

data sharing scenario.<br />

Relationships:<br />

� An Exchange Package refers to an Entity.<br />

� An Exchange Package is disseminated to a Consumer.<br />

� An Exchange Package queries a Query Point.<br />

� An Exchange Package refers to a Payload Definition.<br />

Example: an Exchange Package describes a specific recurring data exchange<br />

involving shipment information.<br />

Entity See the Data Description chapter.<br />

Supplier<br />

Consumer<br />

Payload Definition<br />

Query Point<br />

A Supplier is an entity (person or organisation) that supplies data to a Consumer.<br />

Relationships:<br />

� A Supplier produces an Exchange Package.<br />

Example: a federal agency that supplies data to one or more other federal<br />

agencies.<br />

A Consumer is an entity (person or organisation) that consumes data that is<br />

supplied by a Supplier.<br />

Relationships:<br />

� none<br />

Example: an <strong>Australian</strong> <strong>Government</strong> agency that consumes data from one or<br />

more other <strong>Australian</strong> <strong>Government</strong> agencies.<br />

A Payload Definition is an electronic definition that defines the requirements for<br />

the Payload (data) that is exchanged between a Supplier and a Consumer.<br />

Relationships:<br />

� none<br />

Example: A specific message set expressed as an XML schema or an EDI<br />

transaction set that contains information about a ‘Person’ entity.<br />

A Query Point is an endpoint that provides an interface for accessing and<br />

querying a Data Asset. A concrete representation of a Query Point may be a<br />

specific URL at which a query Web Service may be invoked.<br />

Relationships:<br />

Data Asset See the Data Context section.<br />

� A Query Point accesses a Data Asset. Example: a specific URL at<br />

which a data service may be invoked.<br />

� A Query Point returns a result set specified in an Exchange Package.<br />

<strong>Australian</strong> <strong>Government</strong> <strong>Architecture</strong> <strong>Reference</strong> <strong>Models</strong> <strong>Version</strong> <strong>3.0</strong><br />

227

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!