RE: Proposed edit to identify RDF/XML

> I wonder if a simpler suggestion would be to tie being 
> RDF/XML to either:
> 
> a) being presented with mimetype application/rdf+xml or
> b) having a root element with namespace 
> "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> 
> and not mention the doc production.
> Mentioning the doc production comes back to Beckett's point 
> that the whole grammar needs to be exercised to identify RDF/XML

I would be comfortable going either way.  It's also very easy to change
the suggested text to work as Jeremy suggests.  Here's the text for that
approach:

<text status="suggestion">
<p><a
href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/#section
-grammar-productions">Identifying a conforming RDF/XML document is
optionally left up the system interacting with such a document</a><a
href="#RDFX">[RDFX]</a>.  A GRDDL-aware agent needs to be able to
determine when generic XML documents should be treated as RDF/XML in
order to apply the previous rule. As a result, it has an expanded
awareness of RDF/XML documents that includes XML documents that have a
root element of <code>&lt;rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"/&gt;</code>.
Specifically:</p>

<table border="1">
<tr>
  <th>Normative Statement</th>
</tr>

<tr>

<td class="assertion">
<p>If a representation of an information resource has media type
"application/rdf+xml" or is an XML document such that the XPath
expression

<pre>/*[local-name()="RDF" and
   namespace-uri()="http://www.w3.org/1999/02/22-rdf-syntax-ns#"]</pre>

returns a node-set with a single node, then it is a conforming RDF/XML
document.</p>
</td>

</tr>
</table>
</text>

===================================




Cleveland Clinic is ranked one of the top 3 hospitals in
America by U.S.News & World Report. Visit us online at
http://www.clevelandclinic.org for a complete listing of
our services, staff and locations.


Confidentiality Note:  This message is intended for use
only by the individual or entity to which it is addressed
and may contain information that is privileged,
confidential, and exempt from disclosure under applicable
law.  If the reader of this message is not the intended
recipient or the employee or agent responsible for
delivering the message to the intended recipient, you are
hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited.  If
you have received this communication in error,  please
contact the sender immediately and destroy the material in
its entirety, whether electronic or hard copy.  Thank you.

Received on Monday, 23 April 2007 13:49:30 UTC