Modification History
Release |
Comments |
Release 1 |
This Unit first released with ICP10 Printing and Graphic Arts Training Package version 2.0. Prerequisite unit requirement updated to equivalent current version. Replaces ICPMM491C Create an extensible document. |
Unit Descriptor
This unit describes the performance outcomes, skills and knowledge required to create a well-formed syntax error-free extensible mark-up language document.
Application of the Unit
This unit requires the individual to create an extensible markup language (XML/PPML) document for content publishing that is well-formed, free of errors, meets the needs of the business and is extensible to meet future business needs. For this unit the extensible mark-up language document is the data-store and ICPMM492D Create an extensible style sheet transforms the XML/PPML into screen or print output.
Licensing/Regulatory Information
No licensing, legislative, regulatory or certification requirements apply to this unit of competency.
Pre-Requisites
ICAWEB429A Create a markup language document to specification
Employability Skills Information
This unit contains employability skills.
Elements and Performance Criteria Pre-Content
Element |
Performance Criteria |
Elements describe the essential outcomes of a unit of competency. |
Performance criteria describe the performance needed to demonstrate achievement of the element. Where bold italicised text is used, further information is detailed in the required skills and knowledge section and the range statement. Assessment of performance is to be consistent with the evidence guide. |
Elements and Performance Criteria
1. Define document structure |
1.1 All details required for the job are checked and confirmed against the job specifications 1.2 The mark-up language version and the character encoding used in the document or declaration statement are defined and/or inserted in the document 1.3 An external or internal Document Type Definition (DTD) or mark-up language schema is chosen and correctly wrapped and referenced depending on project requirements 1.4 The root element is correctly defined and all elements are accurately nested 1.5 Attribute types and default values are declared, where necessary, to provide information about the data 1.6 Occurrences of elements are stated and elements of mixed content declared |
2. Confirm validity |
2.1 Start and end tags are included and closed to ensure no element errors 2.2 Namespaces are used to resolve name conflicts 2.3 The document is well-formed, error-free and conforms to the mark-up language syntax rules 2.4 The document conforms to the rules of a Document Type Definition (DTD) or the mark-up language schema |
3. Finalise and test document |
3.1 Character data (CDATA) sections are added to the document structure 3.2 The final document is viewed with a mark-up language parser 3.3 The mark-up language document is well-formed, free of errors and meets the needs of the business 3.4 The document is linked to an extensible style sheet and template and tested 3.5 The document is extensible to meet future business needs |
Required Skills and Knowledge
This section describes the skills and knowledge required for this unit.
Required skills
- OHS in relation to operating machinery such as safely switching off machinery before cleaning is started
- communication of ideas and information applied by detailing attribute types and default values
- collecting, analysing and organising information by forming an error-free document that conforms to the mark-up language syntax rules
- planning and organising activities by defining the document structure prior to confirming validity
- teamwork when maintaining the production process in association with others
- mathematical ideas and techniques by detailing attribute types and default values
- problem-solving skills by developing a mark-up language document free of errors
- use of technology by using industry software to create a mark-up language document.
Required knowledge
- SGML
- standard Generalised Mark-up Language and why it is important
- how SGML relates to XML and PPML
- difference between SGML, PPML and XML and when you use SGML over XML
- XSL
- how Cascading Style Sheets (CSS) and XSL differ
- purpose of XSL is
- HTML
- when to use an extensible mark-up language over HTML and why
- ways to use both with the one set of data
- metadata
- purpose metadata serves within a mark-up language document
- importance of PRISM for content publishing
- PPML
- how Personalised Print Mark-up Language relates to XML.
Evidence Guide
The evidence guide provides advice on assessment and must be read in conjunction with the performance criteria, required skills and knowledge, range statement and the Assessment Guidelines for the Training Package.
Overview of assessment |
|
Critical aspects for assessment and evidence required to demonstrate competency in this unit |
Evidence of the following is essential:
|
Context of and specific resources for assessment |
Assessment must ensure:
|
Method of assessment |
The following assessment method is appropriate for this unit:
|
Guidance information for assessment |
Holistic assessment with other units relevant to the industry sector, workplace and job role is recommended, for example:
|
Range Statement
The range statement relates to the unit of competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included.
Mark-up language may include |
|
Document may include: |
|
Data may include: |
|
PPML may include: |
|
Document purpose may include: |
|
Electronic Publishing may include: |
|
Unit Sector(s)
Multimedia