aseXML Schema Change Request

PREPARED BY:

DOCUMENT REF:<Supplied by ASWG>

VERSION:1.0

DATE:Enter Date

Draft/Final

aseXML Schema Change Request

Version Release History

Version / Date / By / Changes

Glossary

Abbreviation / Description

Contents

1Change Proposal

1.1Description of the proposed change

1.1.1First change description

1.1.2Second change description

1.2Reason for Change

1.3Supplied Documents

1.3.1Business process document

1.3.2Other

1.4Baseline Schema

2Approval Proposal

2.1Proposed Change #1

2.1.1Draft schema

2.1.2Change log

2.1.3Schema change description

2.1.4Impact Summary

2.1.5Developer Test

3Proposal Assessment

3.1Test

3.1.1Test Platforms

3.1.2Test Cases

3.1.3Test Results

3.2Conformance Report

4Issue Register

4.1Status of Issues

5Resolution

5.1ASWG Endorsement

Tables

Table 11, Proposed Changes......

Table 21 Change Log......

Table 22, Impact Summary......

Table 31, Change Proposal Conformance Details......

Table 41, Issues list......

Table 51, ASWG Vote Results......

Figures

Figure 21 Test Figure

1Change Proposal

This Change Proposal … <give business level reason for this change>

1.1Description of the proposed change

The proposed changes are listed in the following table.

Item# / Change Description / Change Type[1]
1 / <Business level description (i.e. Add data elements to transaction … or change constraints on data element … etc)>

Table 11, Proposed Changes

1.1.1First change description

<Description of Change Item #1>

1.1.2Second change description

<Description of Change Item #2>

1.2Reason for Change

<Provide the reason for requesting this change>

1.3Supplied Documents

1.3.1Business process document

<Mandatory. Either identify the location of a suitable Business Process Document, or provide Business Process definitions here…>

1.3.2Other

<List any other supplied documentation (zip with Change Request)>

1.4Baseline Schema

The schema used as a basis for this proposal is …

2Approval Proposal

2.1Proposed Change #1[2]

2.1.1Draft schema

<Identify any draft schema that is supplied with the CR>

2.1.2Change log

The following changes have been implemented in this draft:

Chg # / Item # / Description of change / Filename
1 / All / <list each individual change separately (i.e. added XXX element to XXX Complex Type … or changed constraint on XXX type from 1 to 2… etc>
2 / 1
3 / 1,2

Table 21 Change Log

2.1.3Schema change description

<General description of the schema changes>

2.1.3.1Schema File 1
  • <Details of changes to individual schema files – one per section. Include diagrams as necessary i.e.>

Figure 21 Test Figure

2.1.3.2Schema File 2
  • …

Doc Ref:<Supplied by ASWG> v 1.0 Enter DatePage 1 of 8

aseXML Schema Change Request

2.1.4Impact Summary

This table identifies the files, transactions and versioned types that are potentially impacted as the result of these changes, where:

  • Modified types - is a full list of types changed by this Change Request
  • Derived types – is a list of any types that are derived from a modified type, and are therefore also modified by default
  • Versioned types affected – is a list of all versioned types that will need to have the version attribute updated as a result of this Change Request
  • Transactions potentially affected – is a list of all transactions that contain a modified type, either directly or via a type substitution
  • Schema files affected – is a list of schema files that will be changed in some way as a result of this Change Request.

Modified types / Derived types / Versioned types affected / Transactions potentially affected / Schema files affected

Table 22, ImpactSummary

Doc Ref: <Supplied by ASWG> v 1.0 Enter DatePage 1 of 8

aseXML Schema Change Request

2.1.5Developer Test

2.1.5.1Test Platforms

The new schema has been tested using the following platforms as advised by ASWG:

  • XMLSpy 2004
  • MSXML4 SP1
  • Xerces 1.4.4 and 2.2.1
2.1.5.2Test Cases

<List any sample files provided>

3Proposal Assessment

3.1Test

The ASWG ensures that all recommended parsers on relevant platforms can successfully validate the proposed schema.

3.1.1Test Platforms

Supplied samples have been tested using the following parsers:

  • MSXML 4.0 SP1
  • Xerces 1.4.1
  • Xerces 2.2.1
  • XMLSpy 2004

3.1.2Test Cases

<List samples tested… or ‘as per section 2.1.5.2’>

3.1.3Test Results

<All OK… or note issues>

3.2Conformance Report

The ASWG completes the conformance report validating each proposed new schema file against the published aseXML guidelines.

Schema Filename / Impacted by Item # / Conformance Details
aseXML_r*.xsd / 1,2 / <Conforms… or note non-conformance>

Table 31, Change Proposal Conformance Details

4Issue Register

This section describes any issues that have arisen and any modifications that are made to the original proposal during the Change Process

4.1Status of Issues

Issue# / Item# / Description and Discussion / Status[3] / Resolution
1

Table 41, Issues list

5Resolution

The ASWG votes for endorsement of the options identified in section 2, and the voting results are forwarded to AEMO for approval. When 75% of those ASWG members who voted endorse a specific option, this represents an ASWG Recommendation for that option. AEMO will not reject an ASWG Recommendation without first consulting with the ASWG.

5.1ASWG Endorsement

The results of the ASWG vote are as follows:

Date of Vote: ??/??/????

Option / # Votes / % Vote
Option 1 (section 2.1)
Option 2 (section 2.2)
Option # (section 2.#)
Abstained
Total Members Present

Table 51, ASWG Vote Results

Doc Ref: <Supplied by ASWG> v 1.0 Enter DatePage 1 of 8

[1] Change Type can be one of

  • New
  • Enhancement, or
  • Bug Fix

[2] This section may be repeated if more than one option is considered

[3] Either ‘Open’ or ‘Closed’