{"draft":"draft-nottingham-rfc7320bis-03","doc_id":"RFC8820","title":"URI Design and Ownership","authors":["M. Nottingham"],"format":["HTML","TEXT","PDF","XML"],"page_count":"8","pub_status":"BEST CURRENT PRACTICE","status":"BEST CURRENT PRACTICE","source":"IETF - NON WORKING GROUP","abstract":"Section 1.1.1 of RFC 3986 defines URI syntax as \"a federated and\r\nextensible naming system wherein each scheme's specification may\r\nfurther restrict the syntax and semantics of identifiers using that\r\nscheme.\"  In other words, the structure of a URI is defined by its\r\nscheme. While it is common for schemes to further delegate their\r\nsubstructure to the URI's owner, publishing independent standards\r\nthat mandate particular forms of substructure in URIs is often\r\nproblematic.\r\n\r\nThis document provides guidance on the specification of URI\r\nsubstructure in standards.\r\n\r\nThis document obsoletes RFC 7320 and updates RFC 3986.","pub_date":"June 2020","keywords":["URI structure"],"obsoletes":["RFC7320"],"obsoleted_by":[],"updates":["RFC3986"],"updated_by":[],"see_also":["BCP0190"],"doi":"10.17487\/RFC8820","errata_url":null}