Legacy site for IETF RFC proposals
- Prefix
rfc- Links
- Homepage
Identifier Standards
- Pattern for Local Unique Identifiers
-
Local identifiers in Internet Standard -- IETF Request for Comments should match this regular expression:
^\d+$ - Example Local Unique Identifier
- 5013 Resolve
- Pattern for CURIES
-
Compact URIs (CURIEs) constructed from Internet Standard -- IETF Request for Comments should match this regular expression:
^rfc:\d+$ - Example CURIE
- rfc:5013
Contacts
- Contact
- Missing Contact
- Contributors
-
submitter
Charles Tapley Hoyt
0000-0003-4423-4370
cthoyt
Ontology
A summary of the relations in the Bioregistry schema can be found here.
- In Collection (1)
- Synapse.org external links
Mappings to External Registries
Mappings from records in Bioregistry to external registries comprises the metaregistry. This resource has 1 mapping to an external registry.
| Registry Name | Registry Metaprefix | External Prefix | Curate |
|---|---|---|---|
N2T
|
n2t |
rfc
|
Providers
A provider turns a local unique identifiers from a resource into a URI. Many providers are also resolvable as URLs (i.e., they can be used in a web browser).
The local unique identifier 5013 is used to demonstrate the providers
available for Internet Standard -- IETF Request for Comments. Some providers may use a different example, which is displayed in the table below.
A guide for curating additional providers can be found
here.
| Provider Name | Provider Code | URI |
|---|---|---|
| Internet Standard -- IETF Request for Comments | rfc |
https://tools.ietf.org/rfc/rfc5013 |
| Bioregistry | bioregistry |
https://bioregistry.io/rfc:5013 |
| Name-to-Thing | n2t |
https://n2t.net/rfc:5013 |