Re: XInclude questions--copying attributes

Paul Grosso <paul@paulgrosso.name> writes:
> In our requirements document, we basically gave up on handling
> inclusions that consist of top-level nodes other than elements.
>
> Given that, I suggest we have several options for multiple
> rooted inclusions:
>
> 1.  give up on any attribute copying unless the inclusion
>      is single-rooted.
>
> 2.  do all attribute copying to all top-level elements in
>      the inclusion and let the application deal with multiple
>      identical xml:id's.
>
> 3.  do all attribute copying to all top-level elements in the
>      inclusion except if there is more than one top-level element:
>    a.  don't copy xml:id to any of them
>    b.  only copy xml:id to the first in document order
>
> I suppose a 4th is to define some id fixup, but I'm not even
> going to suggest that, as I think the conclusion in our req doc
> was "that there is no single strategy that would satisfy all
> authors all the time" and that we would let the post-xinclude
> application deal with id fixup.
>
> I lean toward #2 above.

+1

                                        Be seeing you,
                                          norm

-- 
Norman Walsh
Lead Engineer
MarkLogic Corporation
Phone: +1 413 624 6676
www.marklogic.com