Proposal: Update foreign topic to include processing info forgeneralization/specialization use case

[Eric Sirois <esirois@ca.ibm.com>]

The foreign content proposal (#35) for incorporating foreign content in
DITA did not have a use case that covered what would
happen when an DITA document contain foreign content are generalized the
content is not longer valid, when using DTDs for
validation, because the base DTD does not include the foreign vocabularies.

I propose that we hide the foreign content via a processing instruction in
the generalized document. It gets us past the validator
issue. The content could then be re-instated during the specialization
process.  Hiding in a comment was discussed, but there
is no guarantee that tools keep comments in the documents.  Also, it makes
reinstating the foreign content during specialization
much more difficult.

In the case where <foreign> contains an <image>, <object>, or <desc>, they
should not be hidden within the processing instruction.
All content within <unknown> will be hidden in a processing instruction.


Kind regards,
Eric

Original
<p>This is an ellipse.
  <svg>
    <svg:svg width="100%" height="100%" version="1.1"
xmlns="http://www.w3.org/2000/svg";>

<ellipse cx="300" cy="150" rx="200" ry="80"
style="fill:rgb(200,100,50);
stroke:rgb(0,0,100);stroke-width:2"/>

    </svg:svg>
  </svg>.
</p>

Generalized
<p>This is an ellipse.
  <foreign>
     <?dita-hidden
            <svg:svg width="100%" height="100%" version="1.1"
            xmlns="http://www.w3.org/2000/svg";>

            <ellipse cx="300" cy="150" rx="200" ry="80"
            style="fill:rgb(200,100,50);
            stroke:rgb(0,0,100);stroke-width:2"/>

            </svg:svg>
      ?>
  </foreign>.
</p>
Eric A. Sirois
Staff Software Developer
DB2 Universal Database - Information Development
DITA Migration and Tools Development
IBM Canada Ltd. - Toronto Software Lab
Email: esirois@ca.ibm.com
Phone:(905) 413-2841
Blue Pages (Internal)

"Transparency and accessibility requirements dictate that public
information and government
transactions avoid depending on technologies that imply or impose a
specific product or
platform on businesses or citizens" - EU on XML-based office document
formats.