draft of requirement related to versioning

Dear all,

Since I have seen that challenges may arise for localization when an XML
vocabulary evolves, I would like to suggest that we address versioning
(either with the Tag Set, or with the guidelines). Accordingly, I have
put together a draft ...

Best regards,
Christian
---

Challenge/Issue
===============

Localization may suffer if an XML vocabulary evolves, and for example a
new major version is published.

Examples

1. Version 1.0 of an XML vocabulary includes no inline markup. Version
1.1 does include inline markup. If a localization tool is not ready for
inline markup, this change may be a critical issue.

2. Version 1.1 of an XML vocabulary includes two more inline elements
than version 1.0. Accordingly, the localization properties associated
with the XML vocabulary might have to be changed (since the set of
inline elements has changed). Other activities (e.g. modifying a mapping
between the XML vocabulary and XLIFF) might be necessary as well.

Notes
=====

Quick Guideline Thoughts
========================

1. Take care not to break the localization processes due to changes to
the XML vocabulary you are designing. Changes may have an impact on
both, localization directives and localization properties.

2. Maintain associations between your XML vocabulary version (your
XSD/DTD version) and a specific set of localization properties. 

You may start by maintaining the associations in a simple XML file like:

<versionAssocs>
	<assoc>
		<vocabVersion>
			-//O'Reilly//DTD DocBook V3.0-Based Subset
V1.1//EN
		</vocabVersion>
		<locPropVersion>
			-//LocCustomer//General LocProperties 1.1//EN
		</locPropVersion>
	</assoc>
</versionAssocs>

Here, a DocBook customization is associated with version 1.1 for a set
of general localization settings (ie. localization properties) created
by 'LocCustomer' for language English.

Received on Monday, 4 April 2005 08:04:26 UTC