From: Florian Schmaus <flow@gentoo.org>
To: gentoo-dev@lists.gentoo.org,
Alexander Neuwirth <alexander@neuwirth-informatik.de>
Subject: Re: [gentoo-dev] metadata.xml upstream docs as reference to scientific publications/papers
Date: Sun, 17 Sep 2023 20:28:42 +0200 [thread overview]
Message-ID: <1a4e3c3d-6f4a-88d0-b390-4a261019eb27@gentoo.org> (raw)
In-Reply-To: <9bbf6506-3a30-3423-855c-6f42e67c3be0@neuwirth-informatik.de>
[-- Attachment #1.1.1: Type: text/plain, Size: 1015 bytes --]
On 17/09/2023 14.18, Alexander Neuwirth wrote:
> Thanks. Instead of using the lang entry I can imagine these other
> approaches:
>
> 2. Adding something specific to GLEP 68, like `<upstream><reference
> type="doi"> https...`. However that seems like a bit too much work for
> adding something that only a small subset of users (science) cares
> about.
<upstream>
<reference uri='doi:10.17487/rfc6120'/>
</upstream>
sounds perfectly fine.
It would require (minor) adjustments to the schema and DTD. And besides
that, packages that do not have a use for this information do not have
to pay a cost. Hence, I am not sure why you assume its too much work.
> Also integration of parsing with existing tools is an extra
> overhead.
Most XML parsers are non-strict. Which means that they ignore elements
that they do not know. Therefore, the same argument as above can be
made: tools that do not need to extract the information, should not
require any adjustments.
- Flow
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 17273 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2023-09-17 18:28 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
2023-09-17 12:18 ` Alexander Neuwirth
2023-09-17 15:18 ` Ulrich Mueller
2023-09-17 18:28 ` Florian Schmaus [this message]
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=1a4e3c3d-6f4a-88d0-b390-4a261019eb27@gentoo.org \
--to=flow@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