<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-appsawg-uri-get-off-my-lawn" target="https://datatracker.ietf.org/doc/html/draft-ietf-appsawg-uri-get-off-my-lawn-04">
   <front>
      <title>URI Design and Ownership</title>
      <author initials="M." surname="Nottingham" fullname="Mark Nottingham">
         </author>
      <date month="April" day="22" year="2014" />
      <abstract>
	 <t>   RFC3986 Section 1.1.1 defines URI syntax as &quot;a federated and
   extensible naming system wherein each scheme&#x27;s specification may
   further restrict the syntax and semantics of identifiers using that
   scheme.&quot;  In other words, the structure of a URI is defined by its
   scheme.  While it is common for schemes to further delegate their
   substructure to the URI&#x27;s owner, publishing independent standards
   that mandate particular forms of URI substructure is inappropriate,
   because that essentially usurps ownership.  This document further
   describes this problematic practice and provides some acceptable
   alternatives for use in standards.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-appsawg-uri-get-off-my-lawn-04" />
   
</reference>
