This is the mail archive of the
docbook@lists.oasis-open.org
mailing list for the DocBook project.
Re: Re: Adding metainfo to more places
- From: Michael Smith <smith at xml-doc dot org>
- To: docbook at lists dot oasis-open dot org
- Date: Tue, 30 Apr 2002 04:58:07 -0500
- Subject: Re: DOCBOOK: Re: Adding metainfo to more places
- References: <Pine.LNX.4.30.0201161149060.730-100000@peter.localdomain><87ita2oxm3.fsf@nwalsh.com> <3CCE6455.1020800@mandrakesoft.com>
Camille Bégnis <camille@mandrakesoft.com> writes:
> Hi,
>
> has a decision been taken about that point? I've seen no RFE in
> sourceforge list.
> That's something I really need.
The proposal to add a new element named "blockinfo" was accepted. It's
in the 4.2CR1 release of the DTD[1].
There was actually no RFE for it other than the one you filed
originally for adding an *info element to legalnotice. See that (RFE
487482[1]) and the 19 Mar 2002 TC meeting minutes[2] for more info.
From the minutes:
8. Metadata location {10 min}
The proposed list was:
equation, example, figure, informalequation, informalexample,
informalfigure, informaltable, itemizedlist, legalnotice, msgset,
orderedlist, procedure, qandadiv, qandaentry, qandaset, table,
variablelist
And there was no disagreement on the list. Of the proposed names,
"blockinfo" or "blockmeta" and "metainfo" were in a dead heat.
Proposal: adopt blockinfo. Proposal passes without objection.
[1] http://sources.redhat.com/ml/docbook/2002-03/msg00085.html
[2] http://sourceforge.net/tracker/index.php?func=detail&aid=487482&group_id=21935&atid=384107
[3] http://lists.oasis-open.org/archives/docbook-tc/200203/msg00013.html
> Norman Walsh wrote:
> > / Peter Eisentraut <peter_e@gmx.net> was heard to say:
> > | Norman Walsh writes:
> > |
> > |> The DocBook TC has had several discussions about additional places in
> > |> DocBook where it would be beneficial to allow metainfo. Our current
> > |> candidate list of places is:
> > |>
> > |> equation, example, figure, informalequation, informalexample,
> > |> informalfigure, informaltable, itemizedlist, legalnoticeinfo, msgset,
> > |> orderedlist, procedure, qandadiv, qandaentry, qandaset, table,
> > |> variablelist
> > |
> > | I tend to think that every block-level element could have meta info. For
> > | instance, even footnotes and paras could have separate authors or legal
> > | status. It's unlikely to be used often, but not more unlikely than, say,
> > | a procedure with its own metainfo. And if you allow meta info in every
> > | block element it would also make the whole thing more consistent and
> > | easier to learn and use.
> > Adding info to every block element, would have two drawbacks:
> > - It'd make all the content models that much larger which would
> > complicate
> > processing expectations
> > - In mixed content elements, it would not be possible to say
> > something
> > like this:
> > <!ELEMENT para (docinfo?,(#PCDATA|emphasis|...)*)>
> > you'd have to allow docinfo anywhere inside the paragraph:
> > <para>Hi there<docinfo><title>Some Title</title></docinfo>. Isn't
> > this
> > a strange<docinfo><isbn>34234342</isbn></docinfo> paragraph?</para>
> > Be seeing you,
> > norm
> >
>
>
--
Michael Smith, Tokyo, Japan http://sideshowbarker.net
マイク
I felt my life with both my hands
To see if it was there -
--Emily Dickinson (351) http://www.logopoeia.com/ed/