Uniform Resource Characteristic

<p>In <a href="/facts/Internet_Engineering_Task_Force/tIcCsFhX">IETF</a> specifications, a Uniform Resource Characteristic (URC) is a <a href="/facts/Character_string_(computer_science)/4ChJu5WS">string</a> of <a href="/facts/Character_(computing)/X2zKLFFB">characters</a> representing the <a href="/facts/Metadata/qt35z79C">metadata</a> of a <a href="/facts/Uniform_Resource_Identifier/UjyqxTpA">Uniform Resource Identifier (URI)</a>, a string identifying a <a href="/facts/Web_resource/42wbl7QV">Web resource</a>. URC metadata was envisioned to include sufficient information to support <a href="/facts/Persistent_identifiers/hsPK2mkQ">persistent identifiers</a>, such as mapping a <a href="/facts/Uniform_Resource_Name/DCaGkLLY">Uniform Resource Name (URN)</a> to a current <a href="/facts/Uniform_Resource_Locator/pPD5g7Wq">Uniform Resource Locator (URL)</a>. URCs were proposed as a <a href="/facts/Specification_(technical_standard)/xEMUsktp">specification</a> in the mid-1990s, but were never adopted.
</p><p>The use of a URC would allow the location of a Web resource to be obtained from its standard name, via the use of a <a href="/facts/Resolver_(DNS)/rfxdWFsj">resolving service</a>. It was also to be possible to obtain a URC from a URN by the use of a resolving service. The design goals of URCs were that they should be simple to use, easy to extend, and compatible with a wide range of technological systems. The URC syntax was intended to be easily understood by both humans and software.
</p>

Uniform Resource Characteristic open-in-new

Uniform Resource Characteristic