Ignore:
Timestamp:
Jul 18, 2008, 4:43:35 AM (12 years ago)
Author:
julian.reschke@…
Message:

Added safeness to method registration "template" (related to #72)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r284 r286  
    7676<rfc obsoletes="2616" updates="2817" category="std"
    7777     ipr="full3978" docName="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"
    78      xmlns:x='http://purl.org/net/xml2rfc/ext'>
     78     xmlns:x='http://purl.org/net/xml2rfc/ext'
     79     xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
    7980<front>
    8081
     
    422423</t>
    423424<t>
     425  Registrations &MUST; include the following fields:
     426  <list style="symbols">
     427    <t>Method Name (see <xref target="method"/>)</t>
     428    <t>Safe ("yes" or "no", see <xref target="safe.methods"/>)</t>
     429    <t>Pointer to specification text</t>
     430  </list>
     431</t>
     432<t>
    424433  Values to be added to this name space are subject to IETF review
    425434  (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>).  Any document registering
     
    631640
    632641<section title="Safe Methods" anchor="safe.methods">
     642<iref item="Safe Methods" primary="true"/>
    633643<t>
    634644   Implementors should be aware that the software represents the user in
     
    640650   In particular, the convention has been established that the GET and
    641651   HEAD methods &SHOULD-NOT;  have the significance of taking an action
    642    other than retrieval. These methods ought to be considered "safe".
     652   other than retrieval. These methods ought to be considered "<x:dfn anchor="safe">safe</x:dfn>".
    643653   This allows user agents to represent other methods, such as POST, PUT
    644654   and DELETE, in a special way, so that the user is made aware of the
     
    655665
    656666<section title="Idempotent Methods" anchor="idempotent.methods">
     667<iref item="Idempotent Methods" primary="true"/>
    657668<t>
    658669   Methods can also have the property of "idempotence" in that (aside
     
    680691
    681692<section title="OPTIONS" anchor="OPTIONS">
     693  <rdf:Description>
     694    <safe xmlns="urn:ietf:id:draft-ietf-httpbis-p2-semantics#">yes</safe>
     695  </rdf:Description>
    682696  <iref primary="true" item="OPTIONS method" x:for-anchor=""/>
    683697  <iref primary="true" item="Methods" subitem="OPTIONS" x:for-anchor=""/>
     
    742756
    743757<section title="GET" anchor="GET">
     758  <rdf:Description>
     759    <safe xmlns="urn:ietf:id:draft-ietf-httpbis-p2-semantics#">yes</safe>
     760  </rdf:Description>
    744761  <iref primary="true" item="GET method" x:for-anchor=""/>
    745762  <iref primary="true" item="Methods" subitem="GET" x:for-anchor=""/>
     
    779796
    780797<section title="HEAD" anchor="HEAD">
     798  <rdf:Description>
     799    <safe xmlns="urn:ietf:id:draft-ietf-httpbis-p2-semantics#">yes</safe>
     800  </rdf:Description>
    781801  <iref primary="true" item="HEAD method" x:for-anchor=""/>
    782802  <iref primary="true" item="Methods" subitem="HEAD" x:for-anchor=""/>
     
    939959
    940960<section title="TRACE" anchor="TRACE">
     961  <rdf:Description>
     962    <safe xmlns="urn:ietf:id:draft-ietf-httpbis-p2-semantics#">yes</safe>
     963  </rdf:Description>
    941964  <iref primary="true" item="TRACE method" x:for-anchor=""/>
    942965  <iref primary="true" item="Methods" subitem="TRACE" x:for-anchor=""/>
     
    21142137<!--AUTOGENERATED FROM extract-method-defs.xslt, do not edit manually-->
    21152138<!--(START)-->
    2116 <t xmlns:x="http://purl.org/net/xml2rfc/ext">
     2139<t xmlns:x="http://purl.org/net/xml2rfc/ext" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
    21172140    The HTTP Method Registry located at <eref target="http://www.iana.org/assignments/http-methods"/>
    21182141    should be populated with the registrations below:
    21192142  </t>
    2120 <texttable xmlns:x="http://purl.org/net/xml2rfc/ext" align="left">
     2143<texttable xmlns:x="http://purl.org/net/xml2rfc/ext" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" align="left">
    21212144   <ttcol>Method</ttcol>
     2145   <ttcol>Safe</ttcol>
    21222146   <ttcol>Reference</ttcol>
    21232147
    21242148   <c>CONNECT</c>
     2149   <c>no</c>
    21252150   <c>
    21262151      <xref target="CONNECT"/>
     
    21282153
    21292154   <c>DELETE</c>
     2155   <c>no</c>
    21302156   <c>
    21312157      <xref target="DELETE"/>
     
    21332159
    21342160   <c>GET</c>
     2161   <c>yes</c>
    21352162   <c>
    21362163      <xref target="GET"/>
     
    21382165
    21392166   <c>HEAD</c>
     2167   <c>yes</c>
    21402168   <c>
    21412169      <xref target="HEAD"/>
     
    21432171
    21442172   <c>OPTIONS</c>
     2173   <c>yes</c>
    21452174   <c>
    21462175      <xref target="OPTIONS"/>
     
    21482177
    21492178   <c>POST</c>
     2179   <c>no</c>
    21502180   <c>
    21512181      <xref target="POST"/>
     
    21532183
    21542184   <c>PUT</c>
     2185   <c>no</c>
    21552186   <c>
    21562187      <xref target="PUT"/>
     
    21582189
    21592190   <c>TRACE</c>
     2191   <c>yes</c>
    21602192   <c>
    21612193      <xref target="TRACE"/>
Note: See TracChangeset for help on using the changeset viewer.