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.

228<br />

7.8.4 Data Sharing Attributes<br />

This section will expand on the concepts presented above to include attributes that are associated with each<br />

concept. A description will be provided for each attribute, along with an example where necessary for clarity.<br />

Concept Attribute Description Example<br />

Exchange<br />

Package<br />

Identifier 36 A unique string associated with an<br />

Exchange Package for identification<br />

purposes.<br />

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

‘200XCB’<br />

Name The name of an Exchange Package. ‘Bill of Lading Message Set’<br />

Description A description of an Exchange Package.<br />

Classification The security classification for an<br />

Exchange Package.<br />

Frequency The frequency at which the exchange<br />

occurs.<br />

Supplier Identifier A unique string associated with a<br />

Supplier for identification purposes.<br />

Name The name of a Supplier.<br />

Primary<br />

Contact<br />

The name and contact information for<br />

the Supplier’s primary contact for this<br />

particular exchange.<br />

Consumer Identifier A unique string associated with a<br />

Consumer for identification purposes.<br />

Payload<br />

Definition<br />

Name The name of a Consumer.<br />

Primary<br />

Contact<br />

The name and contact information for<br />

the Consumer’s primary contact for this<br />

particular exchange.<br />

Identifier A unique string associated with a<br />

Payload Definition for identification<br />

purposes.<br />

‘U’ (Unclassified)<br />

‘Daily’<br />

‘04091967J’<br />

‘03081956K’<br />

‘B5102078L’<br />

Name The name of a Payload Definition. ‘Bill of Lading XML Schema’<br />

Query Point Identifier 37 A unique string associated with a Query<br />

Point for identification purposes.<br />

http://www.example.com/querypoint3<br />

Name The name of a Query Point. ‘Latest Monthly Report Information’<br />

Description A description of a Query Point.<br />

Query<br />

Languages<br />

A stipulation of the query languages that<br />

are supported by a Query Point (e.g.<br />

SQL-92, CQL (Z39.50), XQuery, HTTP<br />

GET, etc.).<br />

‘SQL-92’<br />

36 The ‘Identifier’ attribute is described at an abstract level in order to be consistent with the abstract nature of the reference model. Therefore, there are no<br />

references to aspects such as identifier uniqueness, representation format or similar. Implementations based on the DRM will introduce such aspects as<br />

needed according to their requirements.<br />

37 For a Query Point, an identifier represents the electronic address at which the Query Point may be accessed.

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

Saved successfully!

Ooh no, something went wrong!