p.s. I forgot to say that, if you do needto get multiple paras inside
your <def>s, it might be a bit less disruptive to redefine its content
model as macro.specialPara rather than model.pLike. Then for the <def>s
which *dont* have multiple paras you won't have to insert one.
Lou Burnard wrote:
> Hmmm... I do find it rather hard to imagine a dictionary entry which
> contains multiple paragraphs of definition for a single entry. Can you
> point us at a sample page? Maybe this work would be better served with a
> more prose like structure, e.g. with "entries" as divs ?
> Elli Mylonas wrote:
>> I am marking up a glossary as part of larger project, and have been
>> using Dictionary markup as the closes kind of matching structure. The
>> dictionary schema works remarkably well for our purposes; we have
>> entries identified by a headword that have some lexical content, a
>> definition, notes and some cross references.
>> The place that we are running into difficulty, however, is that the
>> <def> element, which is used to contain the definition of a word, has
>> the content model macro.paraContent, which effectively restricts it
>> to one paragraph. I'd like to have long definitions with several
>> We will go ahead and use Roma to modify the <def> element to be
>> model.pLike, so it'll do what we need. However, I wanted to bring
>> the paragraphless status of <def> to your attention, in case this is
>> something that others will also see the need for, and perhaps decide
>> it ought to be changed.
>> Should I be using something else? We looked at lists, but they aren't
>> structured enough for our glossary.
>> thanks, --elli
>> [Elli Mylonas
>> Scholarly Technology Group
>> Brown University