Former RFE 100
Keep 'cooked' and 'raw' bibliographic metadata
It is currently possible to mix "raw" and "cooked"
The content models should be adjusted so that this is
no longer possible.
2 April 1999:
Subject: Bibliographic Elements issues
>From some time back:
| Terry and I had a brief discussion about this
recently. We need to
| hash it out.
| 1. Cooked and raw entries should be kept apart to
| processing expectations. I think therefore that
| _not_ be in %bibliocomponent.mix;. (Having it
there allows BiblioSet
| in BiblioMSet.)
(%bibliocomponent.mix; is part of the content model of
and also of BiblioSet and BiblioMSet.) I agree. We
BiblioSet from %bibliocomponent.mix, and add it
directly to the content
model of BiblioEntry; compare the treatment of
BiblioMSet in BiblioMixed.
If there's no objection I'll write up an RFE.
| 2. Should BibliMisc really contain %para.char.mix?
%para.char.mix; is broader than is needed, but I think
this is a
symptom of our need to remodularize, so I'd leave it
alone for now.
Log in to post a comment.