[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gzz] ``canon3_file_format``: A canonical, N3-based file format
From: |
Tuomas Lukka |
Subject: |
Re: [Gzz] ``canon3_file_format``: A canonical, N3-based file format |
Date: |
Wed, 2 Apr 2003 20:28:25 +0300 |
User-agent: |
Mutt/1.4.1i |
On Wed, Apr 02, 2003 at 04:14:21PM +0200, Benja Fallenstein wrote:
> Tuukka Hastrup wrote:
> >On Tue, 1 Apr 2003, Benja Fallenstein wrote:
> >>1. An absolute URI (e.g., ``http://example.org/``).
> >>2. An absolute URI plus a fragment identifier
> >> (e.g., ``http://example.org/#foo``).
> >>3. The empty URI reference (which is a relative URI
> >> refering to the current document).
> >>4. A standalone fragment identifier (e.g., ``#foo``),
> >> refering to a fragment of the current document.
> >
> >Could there be problems with case of the fragment identifier as well? And
> >should we require some canonicalization of the URIs?
>
> No. Our job is to serialize an RDF graph canonically, so that we're
> later able to unserialize it to the same graph. Canonicalizing URIs
> would mean changing the graph.
It'd probably be worth making this an ISSUE in the PEG.
Tuomas
Re: [Gzz] ``canon3_file_format``: A canonical, N3-based file format, Tuukka Hastrup, 2003/04/02