W3C home > Mailing lists > Public > public-i18n-its@w3.org > July to September 2007

Re: ACTION ITEM: draft general section about extending/customizing schemas (http://www.w3.org/International/its/track/actions/1)

From: Felix Sasaki <fsasaki@w3.org>
Date: Wed, 05 Sep 2007 15:48:11 +0900
Message-ID: <46DE512B.1060208@w3.org>
To: "Lieske, Christian" <christian.lieske@sap.com>
CC: public-i18n-its@w3.org

Hi Christian, all,

only editorial, see below.

Lieske, Christian wrote:
> Hi there,
>
> Here's my suggestion. I guess a good place for the text would be the end of
> the overview of the best practices for developers (ie. just before BP 1).
> Possibly we may want to go for a sub-heading like "General Remarks on
> Adapting Schemas".
>
> Thanks to Felix for his input to this.
>
> Cheers,
> Christian
> ===
>
> The "How to do this" parts of this document often contain statements related
> to schema creation or modification. The statements pertain to one of the
> following state-of-affairs:
>
> 1. creating a schema from scratch
> 2. modifying an existing schema 
>
> The following aspects may need to be taken into account when working on both
> of these topics:
>
> 1. Think twice before creating your own schema. Consider strongly existing
> formats such as DITA, DocBook, OpenOffice, XUL, UBL, ... Those formats have
> many insights 'built-in'.
>
> 2. The mechanisms which you can or have to use depend on the schema
> language (DTD, XSD, RelaxNG, ...). Namespace-based modularization of schemas
> for example is hard to realize for DTDs.
>
> 3. Very often each schema formalism provides several possibilities related
> to modification. XSD for example provides statements such as "import",
> "include", or "redefine" as well as mechanisms such as type
> substitution/derivation.
>   

maybe s/each schema formalism/a schema language/

Felix
Received on Wednesday, 5 September 2007 06:48:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:09 UTC