BCP 190
E863223
BCP 190 is a Best Current Practice document in the IETF standards series that provides guidance on the use and management of Uniform Resource Names (URNs).
All labels observed (1)
| Label | Occurrences |
|---|---|
| BCP 190 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T10447638 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BCP 190 Context triple: [RFC 7320, BCPNumber, BCP 190]
-
A.
BCP 195
BCP 195 is an IETF Best Current Practice document that provides modern security recommendations for the use of Transport Layer Security (TLS) and Datagram TLS (DTLS) in Internet protocols.
-
B.
BCP 175
BCP 175 is an IETF Best Current Practice document that defines procedures and policies for managing the DNS root zone’s trust anchor for DNSSEC.
-
C.
BCP 14
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
-
D.
BCP 9
BCP 9 is a Best Current Practice document in the IETF series that defines key procedures and guidelines for the Internet standards process.
-
E.
BCP 40
BCP 40 is an IETF Best Current Practice document that defines modern requirements and guidelines for the use of IPv4 and IPv6 in the Internet.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: BCP 190 Target entity description: BCP 190 is a Best Current Practice document in the IETF standards series that provides guidance on the use and management of Uniform Resource Names (URNs).
-
A.
BCP 195
BCP 195 is an IETF Best Current Practice document that provides modern security recommendations for the use of Transport Layer Security (TLS) and Datagram TLS (DTLS) in Internet protocols.
-
B.
BCP 175
BCP 175 is an IETF Best Current Practice document that defines procedures and policies for managing the DNS root zone’s trust anchor for DNSSEC.
-
C.
BCP 14
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
-
D.
BCP 9
BCP 9 is a Best Current Practice document in the IETF series that defines key procedures and guidelines for the Internet standards process.
-
E.
BCP 40
BCP 40 is an IETF Best Current Practice document that defines modern requirements and guidelines for the use of IPv4 and IPv6 in the Internet.
- F. None of above. chosen
Statements (25)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Best Current Practice document
ⓘ
IETF document ⓘ |
| appliesTo |
IETF participants
ⓘ
URN implementers ⓘ URN namespace maintainers ⓘ |
| concerns |
URN namespace management
ⓘ
URN usage policies ⓘ |
| focusesOn | URNs ⓘ |
| governs |
procedures for URN management
ⓘ
procedures for URN usage ⓘ |
| hasAbbreviation | BCP 190 ⓘ |
| hasDomain |
Internet standards
ⓘ
linked to:
Internet Standard
identifier systems ⓘ |
| language | English ⓘ |
| partOfSeries |
Best Current Practice (BCP)
ⓘ
linked to:
BCP
IETF standards series ⓘ
linked to:
IETF BCP series
|
| providesGuidanceOn |
management of Uniform Resource Names
ⓘ
use of Uniform Resource Names ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
URI
ⓘ
URN namespace registration ⓘ Uniform Resource Identifier ⓘ |
| subjectOf |
Uniform Resource Names
ⓘ
linked to:
Uniform Resource Name
|
| typeOfStandardizationLevel | Best Current Practice ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: BCP 190 Description of subject: BCP 190 is a Best Current Practice document in the IETF standards series that provides guidance on the use and management of Uniform Resource Names (URNs).
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject linked to:
URI Design and Ownership