Unit of Competency Mapping – Information for Teachers/Assessors – Information for Learners

ICPDMT491 Mapping and Delivery Guide
Create an extensible document

Version 1.0
Issue Date: April 2024


Qualification -
Unit of Competency ICPDMT491 - Create an extensible document
Description
Employability Skills
Learning Outcomes and Application This unit describes the skills and knowledge required to create a well-formed syntax error-free Extensible Mark-up Language/Personalised Print Mark-up Language (XML/PPML) document.It applies to individuals who have the responsibility to ensure requirements meet the current and future needs of the business.No licensing, legislative or certification requirements apply to this unit at the time of publication.
Duration and Setting X weeks, nominally xx hours, delivered in a classroom/online/blended learning setting.

Gather evidence to demonstrate consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the digital media technologies field of work and include access to a standalone computer and mark-up language parser.

Assessors must satisfy NVR/AQTF assessor requirements.

Prerequisites/co-requisites
Competency Field
Development and validation strategy and guide for assessors and learners Student Learning Resources Handouts
Activities 		Slides
PPT 		Assessment 1 Assessment 2 Assessment 3 Assessment 4
Elements of Competency Performance Criteria              
Element: Define document structure
  • All details required for job are checked and confirmed against job specifications
  • Mark-up language version and character encoding used in document or declaration statement are defined and/or inserted in document
  • External or internal Document Type Definition (DTD) or mark-up language schema is chosen and correctly wrapped and referenced depending on project requirements
  • Root element is correctly defined and all elements are accurately nested
  • Attribute types and default values are declared, where necessary, to provide information about data
  • Occurrences of elements are stated and elements of mixed content declared
       
Element: Confirm validity
  • Start and end tags are included and closed to ensure no element errors
  • Namespaces are used to resolve name conflicts
  • Checks are performed to ensure that document is well-formed, error-free and conforms to mark-up language syntax rules
  • Document is checked to ensure it conforms to rules of DTD or mark-up language schema
       
Element: Finalise and test document
  • Character Data (CDATA) sections are added to document structure
  • Final document is viewed with mark-up language parser
  • Mark-up language document is well formed, free of errors and meets needs of business
  • Document is linked to extensible style sheet and template, and tested
  • Document is made extensible to meet future business needs
       


Evidence Required

List the assessment methods to be used and the context and resources required for assessment. Copy and paste the relevant sections from the evidence guide below and then re-write these in plain English.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1 Define document structure

1.1 All details required for job are checked and confirmed against job specifications

1.2 Mark-up language version and character encoding used in document or declaration statement are defined and/or inserted in document

1.3 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 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 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 Checks are performed to ensure that document is well-formed, error-free and conforms to mark-up language syntax rules

2.4 Document is checked to ensure it conforms to rules of DTD or mark-up language schema

3 Finalise and test document

3.1 Character Data (CDATA) sections are added to document structure

3.2 Final document is viewed with mark-up language parser

3.3 Mark-up language document is well formed, free of errors and meets needs of business

3.4 Document is linked to extensible style sheet and template, and tested

3.5 Document is made extensible to meet future business needs

Evidence of the ability to:

produce TWO Extensible Mark-up Language (XML) documents that are well-formed, free of errors and meet the job specifications

validate and parse both XML files

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

explain what a Standard Generalised Mark-up Language (SGML) is and what is used for

explain how SGML relates to XML and Personalised Print Mark-up Language (PPML)

explain the differences between SGML, PPML and XML and when to use SGML over XML

describe how Cascading Style Sheets (CSS) and Extensible Stylesheet Language (XSL) differ

explain the purpose of XSL

explain when to use XML over Hyper Text Mark-up Language( HTML) and why

explain how PPML relates to XML

outline ways to use XML and HTML with the one set of data

explain the purpose of metadata within a mark-up language document.

Submission Requirements

List each assessment task's title, type (eg project, observation/demonstration, essay, assignment, checklist) and due date here

Assessment task 1: [title]      Due date:

(add new lines for each of the assessment tasks)

Assessment Tasks

Copy and paste from the following data to produce each assessment task. Write these in plain English and spell out how, when and where the task is to be carried out, under what conditions, and what resources are needed. Include guidelines about how well the candidate has to perform a task for it to be judged satisfactory.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1 Define document structure

1.1 All details required for job are checked and confirmed against job specifications

1.2 Mark-up language version and character encoding used in document or declaration statement are defined and/or inserted in document

1.3 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 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 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 Checks are performed to ensure that document is well-formed, error-free and conforms to mark-up language syntax rules

2.4 Document is checked to ensure it conforms to rules of DTD or mark-up language schema

3 Finalise and test document

3.1 Character Data (CDATA) sections are added to document structure

3.2 Final document is viewed with mark-up language parser

3.3 Mark-up language document is well formed, free of errors and meets needs of business

3.4 Document is linked to extensible style sheet and template, and tested

3.5 Document is made extensible to meet future business needs

Copy and paste from the following performance criteria to create an observation checklist for each task. When you have finished writing your assessment tool every one of these must have been addressed, preferably several times in a variety of contexts. To ensure this occurs download the assessment matrix for the unit; enter each assessment task as a column header and place check marks against each performance criteria that task addresses.

Observation Checklist

Tasks to be observed according to workplace/college/TAFE policy and procedures, relevant legislation and Codes of Practice Yes No Comments/feedback
All details required for job are checked and confirmed against job specifications 
Mark-up language version and character encoding used in document or declaration statement are defined and/or inserted in document 
External or internal Document Type Definition (DTD) or mark-up language schema is chosen and correctly wrapped and referenced depending on project requirements 
Root element is correctly defined and all elements are accurately nested 
Attribute types and default values are declared, where necessary, to provide information about data 
Occurrences of elements are stated and elements of mixed content declared 
Start and end tags are included and closed to ensure no element errors 
Namespaces are used to resolve name conflicts 
Checks are performed to ensure that document is well-formed, error-free and conforms to mark-up language syntax rules 
Document is checked to ensure it conforms to rules of DTD or mark-up language schema 
Character Data (CDATA) sections are added to document structure 
Final document is viewed with mark-up language parser 
Mark-up language document is well formed, free of errors and meets needs of business 
Document is linked to extensible style sheet and template, and tested 
Document is made extensible to meet future business needs 

Forms

Assessment Cover Sheet

ICPDMT491 - Create an extensible document
Assessment task 1: [title]

Student name:

Student ID:

I declare that the assessment tasks submitted for this unit are my own work.

Student signature:

Result: Competent Not yet competent

Feedback to student

 

 

 

 

 

 

 

 

Assessor name:

Signature:

Date:

Assessment Record Sheet

ICPDMT491 - Create an extensible document

Student name:

Student ID:

Assessment task 1: [title] Result: Competent Not yet competent

(add lines for each task)

Feedback to student:

 

 

 

 

 

 

 

 

Overall assessment result: Competent Not yet competent

Assessor name:

Signature:

Date:

Student signature:

Date: