[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Namespaces, Architectural Forms, and Sub-Documents

• From: "Eve L. Maler" <elm@a...>
• To: xml-dev Mailing List <xml-dev@i...>
• Date: Wed, 04 Feb 1998 19:15:34 -0500

This exchange is fascinating.  One comment:

At 05:53 PM 2/4/98 -0500, David Megginson wrote:
>Paul Prescod writes:
> >  * "content model communication" (how do I pass a %cell; content model
> > into my table subdoc)
>
>You're thinking of CALS here.  I'd suggest that we move away from the
>older SGML model of heavily parameterised DTDs (as from heavily
>#IFDEF'ed C header files): remember that one of the arguments for the
>namespace model is to reuse stylesheets and other processing
>specifications -- if a table model can vary its content unpredictably,
>then you will not be able to reuse stylesheets anyway.  Again,
>encapsulation is a big win, and it keeps things easy.

I don't think the problem has anything to do with CALS.  In fact, until
SGML Open came along, it was pretty hard to use the CALS table model as a
module -- it was not designed with this use in mind, and its inflexibility
resulted in dozens or hundreds of DTDs recoding the whole thing just to
change a few features.

Table models, even if they're not CALS, are going to vary their content
unpredictably, because cells typically need to contain markup *inside* them
that is specific to the information domain *outside* the table structure;
they're surrounded coming and going.  (As an aside, I don't think this
means you can't reuse stylesheets; you just sequester the table geometry
stuff from the cell formatting and recode just a little bit of
element-in-context stylesheet code.)

Table cells are a common boundary case of namespace mixing from the text
world, and perhaps there are similar situations in the data world.  I think
that a black-box approach (subdocuments) would require way more overhead
than a unified-model approach in doing "content model communication."

	Eve

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Re: Namespaces, Architectural Forms, and Sub-Documents
    • From: Paul Prescod <papresco@t...>

• References:
  • Re: Namespaces, Architectural Forms, and Sub-Documents
    • From: Paul Prescod <papresco@t...>
  • Namespaces, modules and architectures paper available
    • From: Paul Prescod <papresco@t...>
  • Re: Namespaces, modules and architectures paper available
    • From: Paul Prescod <papresco@t...>
  • Namespaces, Architectural Forms, and Sub-Documents
    • From: David Megginson <ak117@f...>

• Prev by Date: Re: Namespaces, Architectural Forms, and Sub-Documents
• Next by Date: Re: Namespaces, Architectural Forms, and Sub-Documents
• Previous by thread: Re: Namespaces, Architectural Forms, and Sub-Documents
• Next by thread: Re: Namespaces, Architectural Forms, and Sub-Documents
• Index(es):
  • Date
  • Thread