Step 1 – Download latest Schema from UN/CEFACT website – www.unece.org/cefact/
Step 2 – Create copy of code list schema worksheet and rename to match directory being
published
Step 3 – Agree on cut off date with ICG for updated code list schema. Recommend using
the date given to the fully audited CCL.
Step 4 – Validate schema code list date as identified in the schema namespace declaration
for each of the seven code lists used by the unqualified data type schema. The process for
validation of each schema is listed below:
1. IANA Character Set Code List
a. Find latest IANA CHARACTER SETS last updated date found at
http://www.iana.org/assignments/character-sets, and compare against the
version date listed in the IANA Character Set Code List schema from the
current published directory. If the dates are the same no changes are
required, and the previous directory version remains valid and will be used
in the to be published directory.. If the dates are different, then you will
have to redo the schema. Since we have no way of knowing what has
changed, the procedure is a complete replacement of the code list with the
new version. This is accomplished as follows:
i. Worksheet:
1. From the IANA Character set code list webpage, copy the
entire page
2. Paste the copied material into a blank worksheet
3. Delete all lines leading up to the actual character set codes
4. Delete references and people rows at end of sheet
5. Delete all rows for each character set other than the name
and MIBenum number
6. Do a global search and replace to remove all “Name: “ and
“Name “ values
7. Do a global search and replace to remove all “Alias:*” and
“Source:*” values
8. Do a global search and replace to remove all “MB: “ values
9. Each remaining value in column A is either a character set
code and reference, or a MIB number, or supplementary
information about the code, or a blank row.
a. If a character set code and reference, you must
i. copy the reference value and paste in
column b
ii. Delete the spaces and reference value from
column a
b. If a MIB number, cut and paste in the column C of
the preceeding row
c. If supplementary information or a blank row –
delete the row
10. Copy columns A, B, and C to the actual
IANA_CharacterSetCode worksheet and past in the same
columns.
11. Ensure that there is a formula in column D for every row
having a value in column C. If not, copy and paste the
formula from another row.
ii. Schema
1. Open the schema from the latest published directory in the
XML editor. Delete all content related to code values. This
is all content between the <xsd:restriction> and
</xsd:restriction> tags.
2. Copy column D from the worksheet and paste in the XML
editor between the <xsd:restriction> and </xsd:restriction>
tags.
3. Scroll through and make sure there is no innaprorpriate
white space.
4. Increase schema version by 1 in row 7
5. Update schema date in row 8 to represent agreed date for
all new schema. This date should be no earlier than the
code list version date of step 5.
6. Updated code list version date in row 12 to represent IANA
code list version (date)
7. Update schema copyright date in row 19
8. Update xsd:schema xmlnms and targetNamespace to reflect
new IANA code list version (date)
9. Update xsd:schema version to reflect schema version
10. Save schema file using
IANA_CharacterSetCode_XXXXXXXX.xsd where
XXXXXXXX is the IANA code list version (date).
iii. Update all import, schema location, and namespace declarations in
all schema that use this schema.
Status for 08B: OK - http://www.iana.org/protocols/
2. IANA Mime Media Type Code List
a. Validate latest Mime Media Type Code List Schema File date against the
page published dates for each of the Mime Media Types. To accomplish
this, go to http://www.iana.org/assignments/media-types/. On this page
are hyperlinks to each of the directories of content types and subtypes.
You must click on each hyperlink (application, audio, example, image,
message, model, multipart, text, video) and then check the date of that
page. If all dates are older or equal to the schema file name version (date)
of the schema from the last directory, then no changes are required and the
schema is used as is. If any page has a newer date than the schema file
date, you must redo the entire schema. . Since we have no way of
knowing what has changed, the procedure is a complete replacement of
the code list with the new version. This is accomplished as follows:
i. Worksheet:
1. Delete the contents of columns A through D
2. From the IANA MIME Media Types webpage, click and
open the application Content Type and Subtype page
3. copy the entire page
4. Paste the copied material into columns A, B, C where A is
blank, B contains the media type, and C contains the
reference.
5. visually scan all rows and delete any blanks that occur
between application type codes.
6. Type “application” in cell A1 and then copy and paste to all
A cells for which there are application values in column B.
Save your work.
7. Repeat Steps 2 through 6 using the Audio media type, and
substituting the word “audio” for “application” in step 6.
8. Repeat Steps 2 through 6 using the Example media type,
and substituting the word “example” for “application” in
step 6. Note that on the Example page there is a “Other
MIME Media Type Parameters” hyperlink. This is not a
media type.
9. Repeat Steps 2 through 6 using the Image media type and
substituting the word “image” for “application in step 6.
Note that Image Type has 4 columns of information rather
than 3, so in step 4, there will also be additional
information in column D.
10. Repeat Steps 2 through 6 using the Message media type
and substituting the word “message” for “application in
step 6.
11. Repeat Steps 2 through 6 using the Model media type and
substituting the word “model” for “application in step 6.
12. Repeat Steps 2 through 6 using the Multipart media type
and substituting the word “multipart” for “application in
step 6.
13. Repeat Steps 2 through 6 using the Text media type and
substituting the word “text” for “application in step 6.
14. Repeat Steps 2 through 6 using the Video media type and
substituting the word “video” for “application in step 6.
15. Ensure that there is a formula in column E for every row
having a value in column A and B.. If not, copy and paste
the formula from another row.
ii. Schema
1. Open the schema from the latest published directory in the
XML editor. Delete all content related to code values. This
is all content between the <xsd:restriction> and
</xsd:restriction> tags.
2. Copy column E from the worksheet and paste in the XML
editor between the <xsd:restriction> and </xsd:restriction>
tags.
3. Scroll through and make sure there is no innaprorpriate
white space.
4. Increase schema version by 1 in row 7
5. Update schema date in row 8 to represent agreed date for
all new schema. This date should not be prior to the code
list version date from step 5.
6. Updated code list version date in row 12 to represent IANA
code list version (date)
7. Update schema copyright date in row 19
8. Update xsd:schema xmlnms and targetNamespace to reflect
new IANA code list version (date)
9. Update xsd:schema version to reflect schema version
10. Save schema file using
IANA_MIMEMediaType_XXXXXXXX.xsd where
XXXXXXXX is the IANA code list version (date).
iii. Update all import, schema location, and namespace declarations in
all schema that use this schema.
08B Status – Revised Schema dtd 20090304.
3. 3166
a. Validate latest 3166 Code List Schema File date against the ISO list. To
accomplish this, go to
http://www.iso.org/iso/country_codes/updates_on_iso_3166.htm. On this
page is a list of versions. Ensure the version of the latest code list schema
and the newest version listed on this page are the same. ISO also issues
Newsletters with minor changes. Accordingly, you must also check to
make sure the latest version of the code list schema is consistent with the
most recent version of the newsletter. Find the latest newsletter listed for
the latest version (as of 20090305 this is Newsletter VI-4). Compare the
date of this newsletter against the date of the Code List Version on line 12
of the schema. If they are the same, then no change to the schema is
required. If the major version is the same, but if the newsletter is not the
same, then the changes listed in the newsletter(s) must be manually made
in in columns A and B of the ISO_CountryCode worksheet. Once made,
proceed to step b.ii.
b. If the major version is different, then you must redo the schema. This is
accomplished as follows:
i. Worksheet:
1. Delete the contents of columns A and B
2. From the ISO 3166 webpage, copy the contents of the
Country names and ISO 3166-1 alpha-2 code.
3. Paste the copied material into columns A and B where A is
the country name and B contains the ISO code
4. Select columns A and B, and then resort on column B so
that the values are in code sequence.
5. Remove the letters A through F in column A that will
appear.
6. Ensure that there is a formula in column C for every row
having a value in column A and B. If not, copy and paste
the formula from another row.
7. Save your work.
ii. Schema
1. Open the schema from the latest published directory in the
XML editor. Delete all content related to code values. This
is all content between the <xsd:restriction> and
</xsd:restriction> tags.
2. Copy column C from the worksheet and paste in the XML
editor between the <xsd:restriction> and </xsd:restriction>
tags.
3. Scroll through and make sure there is no innaprorpriate
white space.
4. Increase schema version in row 7. Use NDR to determine if
this is a minor or major version change. Generally,
newsletter changes are minor – but not always - and major
version changes are always major.
5. Update schema date in row 8 to represent agreed date for
all new schema. This date should not be prior to the code
list version date from step 5.
6. Updated code list version date in row 12 to represent ISO
version date and date of latest newsletter. For example, if
the latest newsletter is Newsletter VI-4 Name change for Republic
of Moldova and other minor corrections, the date of this newsletter
is 2009-01-07. The code list version is “second edition
2006 with modifications dated 2009-01-07.”.
7. Update schema copyright date in row 19
8. Update xsd:schema xmlnms and targetNamespace to reflect
new values. The namespace version defines iterations and
newsletter numbers. For example, if the latest version is
“second edition 2006” and the latest newsletter is VI-4,
then the namespace declaration and the target namespace
version would be stated as “SecondEdition2006VI-4.”
9. Update xsd:schema version to reflect schema version from
line 7.
10. Save schema file using
ISO_ISOTwoletterCountryCode_XXXXXXXX.xsd where
XXXXXXXX is the namespace version.
iii. Update all import, schema location, and namespace declarations in
all schema that use this schema.
08B Status – updated to reflect reversion of Moldavia name. New version is VI-4.
4. ISO 4217
a. This code list is a little tricky – so be careful.
b. Validate latest 4217 Code List Schema File date against the ISO list. To
accomplish this, you go to the web page
http://www.iso.org/iso/country_codes/updates_on_iso_3166.htm. As
there is no version or date indicator on this page, you must compare every
code. To do so, you must do the following just as if you were redoing the
schema:
i. Worksheet:
1. Open a new worksheet in the code list workbook.
2. From the ISO 4217 webpage, copy the contents of the ISO
4217 currency names and code elements table and paste
into the new worksheet in columns A through D.
3. Delete columns A and D.
4. Sort the contents of the worksheet on column B alphabetic
code.
5. Scroll through each row and delete any rows that contain
duplicate alphabetic codes – other than the principal row.
6. Scroll through each row and delete any rows than contain
no alphabetic codes.
7. Insert new columns A and B in the ISO_CurrencyCode
worksheet and then copy and paste columns A and B from
the temporary worksheet.
8. Compare columns A and B with columns C and D. If there
are no differences, then there are no changes required to the
schema and the current version will be used. If there are
any changes, then continue with the steps below.
9. Ensure that there is a formula in column C for every row
having a value in column A and B. If not, copy and paste
the formula from another row.
10. Save your work.
ii. Schema
1. Open the schema from the latest published directory in the
XML editor. Delete all content related to code values. This
is all content between the <xsd:restriction> and
</xsd:restriction> tags.
2. Copy column C from the worksheet and paste in the XML
editor between the <xsd:restriction> and </xsd:restriction>
tags.
3. Scroll through and make sure there is no innaprorpriate
white space.
4. Increase schema version in row 8. Use NDR to determine if
this is a minor or major version change. Generally,
newsletter changes are minor – but not always - and major
version changes are always major.
5. Update schema date in row 8 to represent agreed date for
all new schema. This date should not be prior to the code
list version date from step 6.
6. Updated code list version date in row 12 to represent code
list version date. This should be the date that the web page
is accessed in the format 2009-01-07.”
7. Update schema copyright date in row 19
8. Update xsd:schema xmlnms and targetNamespace to reflect
new values. The version is the same as the code list version
information from step 6.
9. Update xsd:schema version to reflect schema version from
line 7.
10. Save schema file using
ISO_ISO3AlphaCurrencyCode_XXXXXXXX.xsd where
XXXXXXXX is the namespace version.
iii. Update all import, schema location, and namespace declarations in
all schema that use this schema.
08B Status: New version to reflect changes in codelists.
5. UNECE_CharacterSetEncodingCode
a. Validate latest Character Set Encoding Code (currently 40106) or else
update schema. To accomplish this go to the ISO/TC154-UN/CEFACT
Joint Syntax Working Group Page at http://www.gefeg.com/jswg.
Compare the latest schema version with the latest EDIFACT Syntax
Version/Release number. For example, the current schema version is
40106, and can be identified by the version in the schema file name:
UNECE_CharacterSetEncodingCode_40106.xsd. If the versions are the
same, no changes are required. If the versions are different, then you must
redo the schema. This is accomplished as follows:
i. Worksheet:
1. Delete the contents of columns A, B and C
2. From the JSWG webpage for code 133 webpage, copy the
contents of the code, code name, and definition.
3. Using Paste Special, paste the material into the spreadsheet
as text without formatting. For each code, the information
will be in two cells, each in a different row.
4. Manually manipulate the code list to place the data in
columns A, B, and C as follows:
a. Column A – Code (1, 2, 3 etc)
b. Column B – Code Name ( ASCII 7 bit, ASCII 8 bit,
Code Page 500 (EBDIC Multinational No. 5 etc)
c. Column C – Code Definition (ASCII 7 bit code,
ASCII 8 bit code, Encoding schema for the
repertoire as defined by the code page etc.)
5. Ensure that there is a formula in column D for every row
having a value in column A and B. If not, copy and paste
the formula from another row.
6. Save your work.
ii. Schema
1. Open the schema from the latest published directory in the
XML editor. Delete all content related to code values. This
is all content between the <xsd:restriction> and
</xsd:restriction> tags.
2. Copy column D from the worksheet and paste in the XML
editor between the <xsd:restriction> and </xsd:restriction>
tags.
3. Scroll through and make sure there is no inappropriate
white space.
4. Increase schema version in row 7. Use NDR to determine if
this is a minor or major version change.
5. Update schema date in row 8 to represent agreed date for
all new schema. This date should not be prior to the code
list version date from step 6.
6. Updated code list version date in row 12 to represent syntax
version, syntax release number, Service code list directory
version number. For example, the current version is 40106
where 4 is the syntax version, 01 is the syntax release
number, and 06 is the service code list directory version
number. See: .
http://www.gefeg.com/jswg/data/filename.htm
7. Update schema copyright date in row 14
8. Update xsd:schema xmlnms and targetNamespace to reflect
new values. The namespace version and target namespace
version are the same as the code list version..”
9. Update xsd:schema version to reflect schema version from
line 7.
10. Save schema file using
UNECE_CharacterSetEncodingCode_XXXXX.xsd where
XXXXX is the namespace version.
iii. Update all import, schema location, and namespace declarations in
all schema that use this schema.
08B Status: No changes required.
6. Rec 20 MeasurementUnitCommonCode
a. Go to: http://www.unece.org/cefact/recommendations/rec_index.htm and
identify the latest version of Recommendation Number 20 – Codes for
Units of Measure Used in International Trade. Compare this version
(listed as revision) against the version date of the latest schema. The
version date can be found as the version number in the XML Schema File
Name as follows: UNECE_MeasurementUnitCommonCode_X.xsd where
X is the version number. If they are the same, then no changes are
required to the schema. If they are different, then the schema needs to be
undated. This is accomplished as follows:
i. Worksheet:
1. open the UNECEMeasurementUnit-anex-I-II worksheet
and delete the contents of columns A and B
2. From the
http://www.unece.org/cefact/recommendations/rec_index.h
tm
3. webpage, open the .xls document version of
recommendation 20.
4. Copy columns B and C and paste into columns A and B of
the UNECEMeasurementUNit-anex-I-II worksheet.
5. Delete the header cells in column A and B, and have the
remaining cells shift up.
6. Ensure that there is a formula in column C for every row
having a value in column A and B. If not, copy and paste
the formula from another row.
7. Delete any blank roles.
8. Save your work.
ii. Schema
1. Open the schema from the latest published directory in the
XML editor. Delete all content related to code values. This
is all content between the <xsd:restriction> and
</xsd:restriction> tags.
2. Copy column C from the worksheet and paste in the XML
editor between the <xsd:restriction> and </xsd:restriction>
tags.
3. Scroll through and make sure there is no inappropriate
white space.
4. Increase schema version in row 7. Use NDR to determine if
this is a minor or major version change.
5. Update schema date in row 8 to represent agreed date for
all new schema. This date should not be prior to the code
list version date from step 6.
6. Updated code list version date in row 12 to represent the
version (revision) of the recommendation.
7. Update schema copyright date in row 14
8. Update xsd:schema xmlnms and targetNamespace to reflect
new values. The namespace version and target namespace
version are the same as the code list version..”
9. Update xsd:schema version to reflect schema version from
line 7.
10. Save schema file using
UNECE_MeasurementUnitCommonCode_.xsd where X is
the namespace version.
iii. Update all import, schema location, and namespace declarations in
all schema that use this schema.
08B Status: No change required.
7. 3055
a. Validate if any changes made to 3055 in current directory from previous
directory
b. If no changes, go to step xx.
c. If changes, then you will need to update the worksheet and the schema.
This is accomplished as follows:
i. Worksheet:
1. Open the UNECE 3055 worksheet.
2. Locate the new directory on the
http://www.unece.org/trade/untdid/dXXX/tred/tred3055.ht
m website where XXX is the directory number such as 08a,
08b.
3. Scan the code list and identify all changes.
4. Manually update the worksheet to reflect the changes in
columns A, B and/or C
5. Ensure that there is a formula in column D for every row
having a value in column A and B. If not, copy and paste
the formula from another row.
6. Delete any blank roles.
7. Save your work.
ii. Schema
1. Open the schema from the latest published directory in the
XML editor. Delete all content related to code values. This
is all content between the <xsd:restriction> and
</xsd:restriction> tags.
2. Copy column D from the worksheet and paste in the XML
editor between the <xsd:restriction> and </xsd:restriction>
tags.
3. Scroll through and make sure there is no inappropriate
white space.
4. Increase schema version in row 7. Use NDR to determine if
this is a minor or major version change.
5. Update schema date in row 8 to represent agreed date for
all new schema. This date should not be prior to the code
list version date from step 6.
6. Updated code list version date in row 12 to represent the
version (revision) of the recommendation.
7. Update schema copyright date in row 14
8. Update xsd:schema xmlnms and targetNamespace to reflect
new values. The namespace version and target namespace
version are the same as the code list version..”
9. Update xsd:schema version to reflect schema version from
line 7.
10. Save schema file using
UNECE_AgencyIdentificationCode_XXXX.xsd where
XXXX is the directory version in capital letters. For
example, for Directory 08b, the schema file name would
be:
UNECE_AgencyIdentificationCode_D08B.xsd
Status: Revised for 08b.