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

Re: ITS version attribute

From: Felix Sasaki <fsasaki@w3.org>
Date: Mon, 11 Sep 2006 02:34:19 +0900 (JST)
Message-ID: <3683.24.16.152.99.1157909659.squirrel@webmail.w3.mag.keio.ac.jp>
To: "Sebastian Rahtz" <sebastian.rahtz@oucs.ox.ac.uk>
Cc: public-i18n-its@w3.org

> Felix Sasaki wrote:
>> The current version of the ODD schema generates a mandatory
>> "its:version" attribute. That is correct for its usage at the rules
>> element, but not at a potential root element: imagine that a schema has
>> elements that can be root elements, but also other elements. In that
>> case "its:version" must not be mandatory.
>>
>> Changing
>> <attDef ns="http://www.w3.org/2005/11/its" ident="version" usage="req">
>> to
>> <attDef ns="http://www.w3.org/2005/11/its" ident="version" usage="opt">
>> would break <its:rules> .
>>
>> What do you think?
>>
> the schema is for use with ITS elements, and only mentions the
> the version attribute as it applies to <rules>. It does not
> per se provide schema rules which are to be dumped into
> a host schema. So I don't see it as an issue.
>
> Can you give a use case?

Docbook, which allows you to have e.g. a chapter as a root element, but
also as part of a <book> root element. My (small, but existing) collection
of docbook files have a masterfile with <book> as the root, which includes
via entities chapter. I'd like to validate both (and possibly independent
of each other).

If others don't see this as an issue, I won't insist.

Felix

>
> --
> Sebastian Rahtz
>
> Information Manager, Oxford University Computing Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>
> OSS Watch: JISC Open Source Advisory Service
> http://www.oss-watch.ac.uk
>
>
Received on Sunday, 10 September 2006 17:34:30 UTC

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