- From: Jirka Kosek <jirka@kosek.cz>
- Date: Thu, 16 May 2013 10:56:09 +0200
- To: "Dr. David Filip" <David.Filip@ul.ie>
- CC: Felix Sasaki <fsasaki@w3.org>, "public-multilingualweb-lt@w3.org" <public-multilingualweb-lt@w3.org>
- Message-ID: <51949F29.2030305@kosek.cz>
On 16.5.2013 10:49, Dr. David Filip wrote: >> Spec is just being aligned with common usage. As people introduced their >> own rule elements and no one was surprised about this it was just spec >> which wasn't properly document this shared view of possible extensions. >> > > I do not say it is unnatural, it explicitly introduces a full blown > extensibility mechanism. It is normative because the schema would > invalidate before stuff with such extensions. Please note that as ITS is usually used only in host languages not purely itself, schemas are merely just building blocks. For example current schema its20.nvdl allows extension elements to appear inside its:rules -- schema just accepts any non-ITS element anywhere. > I believe it has potential to become controversial if left for the second > last call. I believe that it should be properly resolved before the second > last call is made. I will push schema chage within minutes, Yves proposed simple sentence describing extensions processing. Do you think that we need something more for proper resolution? Jirka -- ------------------------------------------------------------------ Jirka Kosek e-mail: jirka@kosek.cz http://xmlguru.cz ------------------------------------------------------------------ Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing ------------------------------------------------------------------ OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. ------------------------------------------------------------------ Bringing you XML Prague conference http://xmlprague.cz ------------------------------------------------------------------
Received on Thursday, 16 May 2013 08:56:43 UTC