A better alternative would be something like this: <stable-person-identifier type=“orcid” uri=“https://…” />
This is labelling semantically and providing an extensible format for later support of other schemes. Jay -- Jay Daley IETF Executive Director > On 14 Apr 2025, at 09:56, John R. Levine <jo...@iecc.com> wrote: > > On Sun, 13 Apr 2025, Phillip Hallam-Baker wrote: >> Agree to adding ability to add ORCIDs, strongly disagree as to mechanism. >> >> ORCIDs should be a URI scheme. >> Just tweak the spec to allow multiple URIs. > > No, the point of an <orcid> field is that you know it's an ORCID and can do > things with it that are specific to ORCIDs. If you want a generic URI, you > already have that. > > R's, > John > >> >>> On Sat, Apr 12, 2025 at 5:42 PM John R. Levine <jo...@iecc.com> 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. > > _______________________________________________ > 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