Le Mon, Oct 26, 2009 at 04:05:17PM +0100, Andreas Tille a écrit : > On Tue, Oct 27, 2009 at 12:00:48AM +0900, Charles Plessy wrote: > > since BibTeX issues are perhaps a bit specialised for debian-qa, I propose > > to > > transfer this part of the discussion on debian-scie...@l.d.o, where I > > reopened > > an old thread. > > Well, the question is not really about BibTeX or not. The question is > whether it is a good idea to have a database format as a field value. > If you have the field "Publication" and a complete BibTeX record as > value I somehow wonder whether this is useful in the end or whether we > rather should translate the record in a SQL table.
That is a good question, that I would rephrase: what should be stored, and should everything be exported? For the moment the BibTeX stored reference is a rather experimental feature, and its purpose is also to test the YAML format. As you probalbly noticed, the key parts of the BibTeX reference that allow to construct a weblink to the published article—the digital object identifier (DOI) and the PubMed record ID—have their own YAML mapping: I do not expect the BibTeX reference to be extracted and parsed, nor to be exported to SQL. On the other hand, it can be easily popped out at build time with a Perl oneliner (‘http://lists.debian.org/msgid-search/20090808073608.gf17...@kunpuu.plessy.org’). [For further discussion about how to make nice links on the Blends web sentinels, I propose to elaborate on another list.] There is another volatile meta-data with a much broader scope that could be included in the upstream-metadata.yaml file (or whichever smarter name we give to it), the Debian watch file. All the objections you made above apply. We could either store it raw in a YAML mapping, like: Watch: | version=3 opts=dversionmangle=s/~dfsg// \ http://sf.net/samtools/samtools-([\d\.]*)\.tar\.bz2 Or split the information in multiple mappings: Watch-Version : 3 Watch-Options : dversionmangle=s/~dfsg// Watch-Regexp : http://sf.net/samtools/samtools-([\d\.]*)\.tar\.bz2 While the last option looks more structured, we should really think twice if it makes sense to have the ‘Watch’ metadata in a tabluar SQL database, or if simply storing it raw somewhere else is enough. The same conclusion may apply to similar resources like the BibTeX reference. Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
