Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h7N7Fhqt089648 for <ietf-xml-mime-bks@above.proper.com>; Sat, 23 Aug 2003 00:15:43 -0700 (PDT) (envelope-from owner-ietf-xml-mime@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h7N7FheL089647 for ietf-xml-mime-bks; Sat, 23 Aug 2003 00:15:43 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f
Received: from smtp-relay-7.sea.adobe.com (smtp-relay-7.adobe.com [192.150.22.7]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h7N7Fhqt089638 for <ietf-xml-mime@imc.org>; Sat, 23 Aug 2003 00:15:43 -0700 (PDT) (envelope-from LMM@acm.org)
Received: from inner-relay-1.corp.adobe.com (inner-relay-1 [153.32.1.51]) by smtp-relay-7.sea.adobe.com (8.12.9/8.12.9) with ESMTP id h7N7FbjE008546; Sat, 23 Aug 2003 00:15:37 -0700 (PDT)
Received: from mailsjtest (mailsjtest.corp.adobe.com [153.32.1.139]) by inner-relay-1.corp.adobe.com (8.12.9/8.12.9) with ESMTP id h7N7Fb2R010730; Sat, 23 Aug 2003 00:15:37 -0700 (PDT)
Received: from MasinterT40 ([130.248.182.81]) by mailsjtest.corp.adobe.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0HK200J8P9JG2O@mailsjtest.corp.adobe.com>; Sat, 23 Aug 2003 00:16:29 -0700 (PDT)
Date: Sat, 23 Aug 2003 00:15:37 -0700
From: Larry Masinter <LMM@acm.org>
Subject: re: updated: RDF/XML Media Type registration draft
To: ietf-xml-mime@imc.org, www-rdf-comments@w3.org
Message-id: <001d01c36946$5a4c4180$3c00a8c0@MasinterT40>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.4024
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

"However, in RDF, the thing identified by a URI with
fragment identifier does not bear any particular
relationship to the thing identified by the URI alone.
This differs from some readings of the URI
specification[6], so attention is recommended when
creating new RDF terms which use fragment identifiers."

I confess to have never liked this attempt to use fragment
identifiers in RDF to 'descend into meaning' rather than
to identify a structural fragment; I think it's inconsistent,
and leaves you no way to talk about structural fragments.

The notion that the resource identified by
"http://some.host/some.path#" and "http://some.host/some.path"
are completely unrelated seems pathological.

So not sure 'attention is recommended' captures
the necessary caution.

I think part of the problem is that the draft only
addresses URI references with fragment identifiers
when those URI references are used _as RDF terms_.
But what about other uses? If I have a web page with

<a href="http://some.host/some.path#concept">link
to a concept</a>

what might a legitimate response be to clicking
on that as a link? I can't tell from this document
or the documents it references.








Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h77KQPqt043545 for <ietf-xml-mime-bks@above.proper.com>; Thu, 7 Aug 2003 13:26:25 -0700 (PDT) (envelope-from owner-ietf-xml-mime@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h77KQP0P043544 for ietf-xml-mime-bks; Thu, 7 Aug 2003 13:26:25 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f
Received: from vorpal.notabug.com (qmailr@vorpal.notabug.com [63.149.73.20]) by above.proper.com (8.12.9/8.12.8) with SMTP id h77KQNqt043539 for <ietf-xml-mime@imc.org>; Thu, 7 Aug 2003 13:26:23 -0700 (PDT) (envelope-from me@aaronsw.com)
Received: (qmail 24302 invoked from network); 7 Aug 2003 20:26:25 -0000
Received: (ofmipd 12.207.74.63); 7 Aug 2003 20:26:03 -0000
Date: 7 Aug 2003 15:26:23 -0500
Message-Id: <69ED15D9-C915-11D7-A0FB-0003936780B2@aaronsw.com>
From: "Aaron Swartz" <me@aaronsw.com>
To: ietf-xml-mime@imc.org, ietf-xml-mime@imc.org, www-rdf-comments@w3.org
Cc: "Dave Beckett" <dave.beckett@bristol.ac.uk>, "Graham Klyne" <GK@NineByNine.org>
Mime-Version: 1.0 (Apple Message framework v578)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit
Subject: updated: RDF/XML Media Type registration draft
X-Mailer: Apple Mail (2.578)
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

I've updated the draft to reflect all the comments I've received. Here  
are the changes I've made:

1. Changed type to be "rdf " so as to be consistent with the syntax doc.

2. Deleted section on social meaning.

3. Refers to Concepts instead of Model Theory.

4. Added paragraph to interoperability considerations:
     RDF is intended to allow common information to be exchanged between
     disparate applications.  A basis for building common understanding  
is
     provided by <xref target="W3C.rdf-mt">a formal semantics</xref>, and
     applications that use RDF should do so in ways that are consistent  
with this.

5. Added paragraph to section on Fragment Identifiers:
     More details on RDF's view of fragment identifiers can be found in  
the
     section "Fragment Identifiers" of <xref  
target="W3C.rdf-concepts">the
     RDF Concepts document</xref>.

The updated version is available at:
http://www.aaronsw.com/2002/draft-swartz-rdfcore-rdfxml-mediatype 
-03.html

Unless there are any objections, I plan to submit it as an updated  
Internet-Draft. We'll probably do this again after the RDF specs go to  
REC. Thanks for all your help.
-- 
Aaron Swartz: http://www.aaronsw.com/