OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE : [docbook] Question: address within entry


	Hello,

	Glad to see docbook list again, in hope to be allowed to post.

> Not that I know of.
> The DocBook Technical Committee has an active agenda
> item to review which info elements are appropriate
> for inclusion in inline content outside of the *info
> elements.  I'll add the content of <entry> to that
> discussion.

	I pick up this thread for a more general question on *info.

	What is the reason why the info block is sometimes coming after
the title (ex: article, book), and before everything in some other cases
(ex: section, bibliography)?
	To continue, is it in your projects to provide a generic info
wrapper? This may become very useful with includes (example: as an
everywhere signature in a project, with some automatic revhistory
fill-in).
	Related to this topic, I was sad to read: "Future Changes,
ArticleInfo will be dropped from the content model of BiblioEntry". I
understand that the name is not exactly the best (see above), but the
wrapper allows keeping of important information from bibliographic
systems (revhistory, keyword, subjects ...). An info block is a good
place for that (outside of rendering), and automatic extraction from an
author bibliography may be used by a full bibliographic system (or an
indexation engine).

	For the Committee discussions, I can also suggest to think about
an inline <subject concept="sujet" thesaurus="rameau">subject</subject>,
where @concept is the authorized form of "subject" in the "rameau"
thesaurus (I need to implement the iso 5964 standard on thesauri, I
would be glad to do it with full compatible docbook).
	I also notice that <revhistory/> could be in lots of places. I'm
using it because it's the only place to find <date/> as a list (in spite
of the <revnumber/>). <calendar/>, <chronology/> or <history/> could be
better to explain my usages. It's of course of academic or journalistic
interest, perhaps software documentation can also find usage of it.

	Fred.




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]