[
Lists Home |
Date Index |
Thread Index
]
Arjun Ray wrote:
> | 1. avoiding collisions
>
> A non-problem.
Really?
You probably know the XSLFO spec includes an element named
instream-foreign-object, which is intended as a sort of hook
for FO processors to provide functionality which may otherwise
be awkward to provide in XSLFO. Famous examples include
embedding SVG and MathML but also less widespread stuff like
charts, diagrams or graphs. It is common that the embedded
data is XML, using a vocabulary which was in general
designed independently from XSLFO. A vocabular for diagrams
can conceivably contain a block element, which has most
probably a different content model and often a different
processing expectation that XSLFO's block element.
People have expectations about the environment and tools which
handle their XML, in this case the XSLFO with an embedded
diagram description:
- Use a generic software which can be easily customized to
provide all kind of editing support, particularly what is
known as schema-directed editing on XML-DEV.
- Use generic tools like XSLT processors to manipulate the
XML, for example changing the colors on the diagram's blocks.
Would you please elaborate why any of the developers and
the users of the tools mentioned above, possibly including
the FO processor writer, should see name collisions as
non-problem?
J.Pietschmann
|
