> On Sun, 17 Sep 2023, Florian Schmaus wrote:
>
>
>
> sounds perfectly fine.
Don't use an attribute if you can put the information in the (otherwise
empty) element. Especially, when other elements like already do it
that way.
> It would require (minor) adjustments to the schema and
On 9/17/23 20:28, Florian Schmaus wrote:
sounds perfectly fine.
Ideally I'd not limit it to only doi but also arxiv, zenodo, inspirehep.
They can all be referenced by https://... . I agree a specific type is
kind of unnecessary. However, the same paper can be referenced by all of
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 `type="doi"> https...`. However that seems like a bit too much work for
adding something that only a small subset of users
> On Sun, 17 Sep 2023, Alexander Neuwirth wrote:
> Thanks. Instead of using the lang entry I can imagine these other
> approaches:
> 1. doi/arxiv/... links could also easily be plugged in custom upstream
> remote ids, but that also feels a bit wrong since all other [upstream
> remote
>
Thanks. Instead of using the lang entry I can imagine these other
approaches:
1. doi/arxiv/... links could also easily be plugged in custom upstream
remote ids, but that also feels a bit wrong since all other [upstream
remote
> 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
> |https://doi.org/...|. Integration with
> |epkginfo|/|equery meta| works nicely out of the box. However,
>
Dear Larry,
I am looking for a way to link scientific publications to
ebuilds/packages. The easiest, but hacky way right now is to use the
|https://doi.org/...|. Integration with
|epkginfo|/|equery meta| works nicely out of the box. However, currently
|pkgcheck| and/or the XML format
