NTISthis.com

Evidence Guide: ICPDMT491 - Create an extensible document

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICPDMT491 - Create an extensible document

What evidence can you provide to prove your understanding of each of the following citeria?

Define document structure

  1. All details required for job are checked and confirmed against job specifications
  2. Mark-up language version and character encoding used in document or declaration statement are defined and/or inserted in document
  3. External or internal Document Type Definition (DTD) or mark-up language schema is chosen and correctly wrapped and referenced depending on project requirements
  4. Root element is correctly defined and all elements are accurately nested
  5. Attribute types and default values are declared, where necessary, to provide information about data
  6. Occurrences of elements are stated and elements of mixed content declared
All details required for job are checked and confirmed against job specifications

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

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

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

External or internal Document Type Definition (DTD) or mark-up language schema is chosen and correctly wrapped and referenced depending on project requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Root element is correctly defined and all elements are accurately nested

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Attribute types and default values are declared, where necessary, to provide information about data

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Occurrences of elements are stated and elements of mixed content declared

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Confirm validity

  1. Start and end tags are included and closed to ensure no element errors
  2. Namespaces are used to resolve name conflicts
  3. Checks are performed to ensure that document is well-formed, error-free and conforms to mark-up language syntax rules
  4. Document is checked to ensure it conforms to rules of DTD or mark-up language schema
Start and end tags are included and closed to ensure no element errors

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Namespaces are used to resolve name conflicts

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Checks are performed to ensure that document is well-formed, error-free and conforms to mark-up language syntax rules

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

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

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Finalise and test document

  1. Character Data (CDATA) sections are added to document structure
  2. Final document is viewed with mark-up language parser
  3. Mark-up language document is well formed, free of errors and meets needs of business
  4. Document is linked to extensible style sheet and template, and tested
  5. Document is made extensible to meet future business needs
Character Data (CDATA) sections are added to document structure

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Final document is viewed with mark-up language parser

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

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

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

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

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document is made extensible to meet future business needs

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

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

Required Skills and Knowledge

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.