Hi John -
AFAICT from the ORCID website, one use of ORCIDs is to mask personal
identity information. That suggests some policy is needed.
I think adding the field is fine. And I'm staying out of the
bikeshedding discussions about exactly how that field is formatted.
What I would like in any document that adds this support (as well as in
the supporting RFC editor policies):
1) A requirement that the database entry for an RFC-included ORCID have
at least sufficient public visibility to map the author name and ideally
country to the provided ORCID. (I haven't spent any time looking at the
ORCID system, so I'm unclear just how extensive its restriction and
privacy settings are).
2) A discussion of why the RFC series does not permit anonymity in its
authorships. (Of course, if the community thinks anonymity should be
permitted, then that discussion needs to happen as well as defining the
limits of said anonymity).
3) A check by the RFC editor to make sure that we're not accidentally
blowing someones cover by publishing a document that includes a mapping
between a mostly-non-public-data ORCID and the associated data for the
<author/> block.
4) Optional: Maybe make it a requirement for each RFC author to have an
ORCID? And enlist the RFC editor in helping that happen?
5) A quick review by the RSCE on whether ORCIDs are or will be a "stable
resource". E.g. how are they funded, who owns the database? Can the
database be sold? Is there an escrow and recovery process? Is there a
backing established organization (e.g. EDUCOM?).
6) A process for back filling existing authors info?
Later, Mike
On 4/12/2025 5:41 PM, John R. Levine wrote:
You may have seen some discussions about ORCIDs on the main IETF list.
Here's a concrete proposal to add them to rfcxml.
I propose to add a new sub-element to the author element called orcid.
Its formal definition would be text, just like email or uri, but the
idea is that it contains your ORCID, like this:
<author fullname="John Levine">
<organization/>
<address>
<postal>
<country>US</country>
</postal>
<email>standa...@standcore.com</email>
<orcid>0000-0001-7553-5024</orcid>
</address>
</author>
I realize you can put the ORCID URI in the URI field, or if you're
Carsten you can sneak it into the email field, but the idea is that
the contents of the <orcid> element is an ORCID and nothing else.
It'd be rendered as a line in the address, probably with a link to the
orcid.org site in the HTML, e.g.:
ORCID <a
href="http://orcid.org/0000-0001-7553-5024";>0000-0001-7553-5024</a>
As far as I can tell this would be backward compatible and should not
be hard to implement. The various markdown processors would have to
add a way to put in your ORCID but again that doesn't seem hard.
Regards,
John Levine, jo...@taugh.com, Primary Perpetrator of "The Internet for
Dummies",
Please consider the environment before reading this e-mail. https://jl.ly
_______________________________________________
rfc-interest mailing list -- rfc-interest@rfc-editor.org
To unsubscribe send an email to rfc-interest-le...@rfc-editor.org
_______________________________________________
rfc-interest mailing list -- rfc-interest@rfc-editor.org
To unsubscribe send an email to rfc-interest-le...@rfc-editor.org
