Technically speaking, this is a link relation type, as defined in RFC 8288 [1].
[1]: https://www.rfc-editor.org/rfc/rfc8288#section-2.1 A registry is at: https://www.iana.org/assignments/link-relations/ [2]: https://authors.ietf.org/rfcxml-vocabulary#address [3]: https://authors.ietf.org/rfcxml-vocabulary#uri With the existing RFCXML vocabulary, in the content model (“schema”) for <address [2], we would turn the uri? …into uri* and add a rel attribute to the content model for <uri [3]: <uri rel="me">https://orcid.org/0000-0001-9527-7181</uri> I’ll leave it to the Web Linking connoisseurs to dig out the right relation type (or to register another one for this specific purpose). Of course, I’d prefer the URI to be in an href attribute, but that’s not how RFCXML was defined. Grüße, Carsten > On 2025-04-13, at 16:01, Salz, Rich <rsalz=40akamai....@dmarc.ietf.org> wrote: > > Maybe this could be made a bit more generic? > > Such as...: > > <bikeshed-here type="orcid" > href=" > http://orcid.org/0000-0001-7553-5024";>0000-0001-7553-5024</bikeshed-here> > > ...which would make it a "typed" <eref/>. > > Is that really less work? I don’t know, can people add any type attribute > without IETF working on it? > _______________________________________________ > 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
