- From: Innovimax W3C <innovimax+w3c@gmail.com>
- Date: Thu, 24 Nov 2011 13:24:28 +0100
- To: "Henry S. Thompson" <ht@inf.ed.ac.uk>
- Cc: public-xml-core-wg@w3.org
- Message-ID: <CAAK2GfGo6ppRnn1HJfdb=MgWE39Xztpkf1gqxS0cM46XNYfKtQ@mail.gmail.com>
I think we should solve the simple TOP level story and let the include problem on the side Mohamed On Thu, Nov 24, 2011 at 1:20 PM, Henry S. Thompson <ht@inf.ed.ac.uk> wrote: > Innovimax W3C writes: > > > We should just ask the Browser vendor to do the same > > > > The idea being : they generate with the first PI > > And they add the list of other PI such that the user can change the > content > > of the page > > The problem is, the CSS story depends on the fact that CSS has a > well-defined mechanism for merging stylesheets and resolving any > resulting conflicts. XSLT doesn't, or rather, it has several, and we > would need to specify in some detail which mechanism, and how. Would > we use xsl:include semantics, or xsl:import? Or, for example, suppose > there were _three_ xmlss PIs with the same title, would the first > include the second and third, or the first include the second which > includes the third, or the opposite order, or . . .? > > ht > -- > Henry S. Thompson, School of Informatics, University of Edinburgh > 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440 > Fax: (44) 131 651-1426, e-mail: ht@inf.ed.ac.uk > URL: http://www.ltg.ed.ac.uk/~ht/ > [mail from me _always_ has a .sig like this -- mail without it is forged > spam] > -- Innovimax SARL Consulting, Training & XML Development 9, impasse des Orteaux 75020 Paris Tel : +33 9 52 475787 Fax : +33 1 4356 1746 http://www.innovimax.fr RCS Paris 488.018.631 SARL au capital de 10.000 €
Received on Thursday, 24 November 2011 12:24:59 UTC