Re: XInclude enhancements?

We should definitely find a substitute do entities that works well  in such
case

Mohamed

On Fri, Jul 22, 2011 at 8:08 PM, Norman Walsh <ndw@nwalsh.com> wrote:

> XInclude is useful for transclusion, but it's not sufficient to handle
> some classes of problems that commonly arise. In particular, copying
> content can introduce duplicate ID values.
>
> I wonder if there'd be any interest in extending XInclude to address
> some of these problems. The DocBook Technical Committee has spent some
> time gathering requirements[1] and devising possible solutions[2] to
> address transclusion.
>
> But it seems a shame to invent DocBook-specific markup to handle
> problems that are clearly true of most XML vocabularies.
>
> Supporting some kind of special ID/IDREF processing[3] would go a long
> way towards making XInclude more useful. (Given a more powerful
> XInclude, I think some of the other requirements raised in the DocBook
> discussions could be addressed with a new XPointer scheme.)
>
> Worth considering?
>
>                                        Be seeing you,
>                                          norm
>
> [1] http://docbook.org/docs/transclusion-requirements/
> [2] http://docbook.org/docs/transclusion/
> [3] http://docbook.org/docs/transclusion/#d6e180
>
> --
> Norman Walsh
> Lead Engineer
> MarkLogic Corporation
> Phone: +1 413 624 6676
> www.marklogic.com
>



-- 
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 €