From: Ulrich Mueller <ulm@gentoo.org>
To: Alexander Neuwirth <alexander@neuwirth-informatik.de>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] metadata.xml upstream docs as reference to scientific publications/papers
Date: Fri, 15 Sep 2023 12:15:37 +0200 [thread overview]
Message-ID: <w6ga5tnagja.fsf@uni-mainz.de> (raw)
In-Reply-To: <e1a684e3-42e4-12e8-2fa3-a38339e3d6ad@neuwirth-informatik.de> (Alexander Neuwirth's message of "Fri, 15 Sep 2023 11:31:24 +0200")
>>>>> On Fri, 15 Sep 2023, Alexander Neuwirth wrote:
> I am looking for a way to link scientific publications to
> ebuilds/packages. The easiest, but hacky way right now is to use the
> |<doc lang="doi">https://doi.org/...</doc>|. Integration with
> |epkginfo|/|equery meta| works nicely out of the box. However,
> currently |pkgcheck| and/or the XML format complains about repeated
> |lang| entries and does not allow long |lang| attributes (i.e.
> |lang="inspirehep"| fails understandably).
Please don't do this. The lang attribute is of type xs:language [1]
so it must be a valid BCP 47 language tag.
As a matter of fact, "doi" happens to be a valid tag for the Dogri
language [2], but this isn't helpful either.
[1] https://gitweb.gentoo.org/data/xml-schema.git/tree/metadata.xsd?id=db829cfdb40ae0a0034848cce38ee741a7c8d68c#n257
[2] https://www.loc.gov/standards/iso639-2/php/langcodes_name.php?code_ID=117
next prev parent reply other threads:[~2023-09-15 10:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 9:31 [gentoo-dev] metadata.xml upstream docs as reference to scientific publications/papers Alexander Neuwirth
2023-09-15 10:15 ` Ulrich Mueller [this message]
2023-09-17 12:18 ` Alexander Neuwirth
2023-09-17 15:18 ` Ulrich Mueller
2023-09-17 18:28 ` Florian Schmaus
2023-09-17 19:06 ` Alexander Neuwirth
2023-09-17 20:55 ` Ulrich Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=w6ga5tnagja.fsf@uni-mainz.de \
--to=ulm@gentoo.org \
--cc=alexander@neuwirth-informatik.de \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox