One document matched: draft-snell-atompub-inline-01.xml

<?xml version='1.0'?>
 <!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
    <!ENTITY rfc2119 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'> 
    <!ENTITY rfc4287 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.4287.xml'> 
    <!ENTITY rfc3986 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml'>  
    <!ENTITY rfc3023 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3023.xml'>  
    <!ENTITY rfc3548 PUBLIC '' 
      'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3548.xml'>  
    <!ENTITY xml PUBLIC ''
      'http://xml.resource.org/public/rfc/bibxml4/reference.W3C.REC-xml-20040204.xml'> 
     <!ENTITY xmlnames PUBLIC ''
      'http://xml.resource.org/public/rfc/bibxml4/reference.W3C.REC-xml-names-19990114.xml'> 
    <!ENTITY xmlbase PUBLIC ''
      'http://xml.resource.org/public/rfc/bibxml4/reference.W3C.REC-xmlbase-20010627.xml'>
]>
<?rfc compact="yes" ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?>
<rfc category="info" ipr="trust200811" updates="4287" docName="draft-snell-atompub-inline-01.txt"> 
<front> 
<title abbrev="Atom inline">The Atom Link "inline" Extension</title> 
<author initials="J.M." surname="Snell" fullname="James M Snell"> 
<organization></organization> 
<address> 
<postal> 
<street></street> 
<city></city> <region></region> <code></code> 
<country></country> 
</postal> 
<phone></phone> 
<email>jasnell@us.ibm.com</email> 
<uri>http://ibm.com</uri> 
</address> 
</author> 
<date month="November" year="2010" /> 
<area>General</area> 
<keyword>I-D</keyword> 
<keyword>Internet-Draft</keyword> 
<keyword>XML</keyword> 
<keyword>Extensible Markup Language</keyword> 
<keyword>Atom</keyword> 
<keyword>RSS</keyword> 
<keyword>Syndication</keyword> 
<abstract><t>This specification adds a mechanism to the Atom Syndication Format 
which publishers of Atom Feed and Entry documents can use to embed representations
of linked resources into a child element of the atom:link element.</t></abstract> 
</front> 
<middle> 
<section title="Introduction"> 
 
<t>This specification introduces a mechanism to the Atom Syndication Format 
which publishes of Atom document can use to embed representations of linked 
resources into a child element of the atom:link element.</t>
  
</section> 
 
<section title="Notational Conventions"> 
 
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", 
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be 
interpreted as described in BCP 14, <xref target="RFC2119" /></t> 
 
<t>This specification uses XML Namespaces <xref target="W3C.REC-xml-names-19990114"/> 
to uniquely identify XML element names.  It uses the following namespace prefix 
for the indicated namespace URI;</t> 
 
<figure><artwork><![CDATA[ 
 "atom": "http://www.w3.org/2005/Atom" 
]]></artwork></figure> 
 
</section> 
 
<section title="The 'atom:inline' element"> 
 
<t>The atom:inline element MAY be used as the child of an atom:link element to
embed representations of the resource referenced by the containing atom:link.</t> 
 
<figure><artwork><![CDATA[ 
  inline = element atom:inline {
    (text|anyElement)*
  } 
]]></artwork></figure> 
 
<t>An atom:link element MUST NOT contain more than one atom:inline element.</t> 
 
<t>If the value of the containing link element's type attribute begins with 
"text/" (case insensitive), the content of atom:inline  MUST NOT contain 
child elements.</t>

<t>If the value of the link element's type attribute is an XML media type 
<xref target="RFC3023" /> or ends with "+xml" or "/xml" (case insensitive), 
the content of the atom:inline element MAY include child elements and SHOULD be 
suitable for handling as the indicated media type. This would normally mean 
that the atom:inline element would contain a single child element that would 
serve as the root element of the XML document of the indicated type.</t>

<t>If the value of the link element's type attribute is "application/json" or 
ends with "+json" or "/json" (case insensitive), and the character-set encoding
of the enclosing Atom document is UTF-8, UTF-16 or UTF-32, the content of the 
atom:inline element MUST be the plain-text representation of the linked JSON
document. The content MAY be preceded and followed in the atom:inline element
by white space.</t>

<t>For all other values of the type attribute, the content of atom:inline MUST 
be a valid Base64 encoding, as described in <xref target="RFC3548"/>, section 3. When decoded,
it SHOULD be suitable for handling as the indicated media type. In this case, 
the characters in the Base64 encoding MAY be preceded and followed in the
atom:inline element by white space, and lines are separated by a single newline
(U+000A) character. </t>

<figure><artwork><![CDATA[ 
  <feed xmlns="http://www.w3.org/2005/Atom"> 
     ...
     <entry>
       ...
       <link type="text/plain" href="example.txt">
         <inline>This is an example</inline>
       </link>
       <link type="application/json" href="entry.json">
         <inline>{"a":"foo","b":"bar","c:"baz"}</inline>
       </link>
       <link type="image/jpeg" href="entry.jpg">
         <inline>ew0KICAiaWQiOiJodHRwOi8vZXhhbXBsZS5vcm
cvZm9vIiwNCiAgInRpdGxlIjoiZm9vIg0KfQ==</inline>
       </link>
       <link type="application/atom+xml" href="entry.xml">
         <inline>
           <feed>
             ...
           </feed>
         </inline>
       </link>
       ...
     </entry>
     ...
  </feed> 
]]></artwork></figure> 

</section> 
 
<section title="Security Considerations"> 

<t>TBD</t>

</section> 
 
<section title="IANA Considerations"> 
 
<t>There are no IANA considerations for this document.</t>  
  
</section> 
 
<section title="Acknowledgements"> 
<t>The author gratefully acknowledges the feedback from the members of the 
Atom Publishing Format and Protocol working group during the development of 
this specification.</t> 
</section> 
 
</middle> 
 
<back> 
<references title="Normative References"> 
  &rfc2119;
  &rfc3986;
  &rfc4287;
  &rfc3023;
  &rfc3548;
  &xml;
  &xmlbase;
  &xmlnames;
</references> 
</back> 
</rfc>