W3C home > Mailing lists > Public > www-rdf-interest@w3.org > January 2001

Re: Dropping the redundant colon in N3

From: Sean B. Palmer <sean@mysterylights.com>
Date: Thu, 1 Feb 2001 01:27:50 -0000
Message-ID: <00b501c08bee$c1ad20c0$1ddc93c3@z5n9x1>
To: "Seth Russell" <seth@robustai.net>
Cc: "Aaron Swartz" <aswartz@swartzfam.com>, "Tim Berners-Lee" <timbl@w3.org>, <www-rdf-interest@w3.org>
"Seth Russell" wrote:-

> [http://purl.org/dc/elements/1.1/] = [http://purl.org/dc/elements/1.1/#].

I'm really confused now... Why are you adding the "#" after it for, and
calling them equivelent? These namespaces make completely different URIs
when pieced back together again: http://purl.org/dc/elements/1.1/title is
totally different from http://purl.org/dc/elements/1.1/#title

BTW: I believe I was mistaken in thinking that DC redirects as appropriate.
A better example would be the Wordnet namespace:-

     http://xmlns.com/wordnet/1.6/

Note that http://xmlns.com/wordnet/1.6/word *does* exist, whereas
http://xmlns.com/wordnet/1.6/#word does not.

> Your completely right .. sorry i was confused.  Do you think I fixed it
by
> using square brackets to delimit URI ?

That is quite a good idea. I wonder though about having [ ] to imply a node
one minute, and then a URI the next. Is that O.K. - i.e. will people
understand that?
It does make the coding neat, but I suppose it would be very difficult to
get a program to grok tht if you have different amount of elements inside
the "[ ]" it means a completely different thing altogether. Still, it's
probably better than using <> because at least we can use it inside XML
now. I suppose the next step is to ask: "what MIME type should N3 have?".
text/plain for the moment I guess, but that implies that it is just "text,
and not code", which it clearly isn't.

> > I believe that percentage signs ("%") are only allowed to escape
> > characters in URIs, so why not use them?
>
> The more weird characters you throw in the stream, the more it looks
> like cyber gibberish and the more difficult it becomes for humans to
> read and the more it offends the eye.

Very good point.

> How many times have you not been able to vance on a url in
> a email because the author abutted it to a period.

Millions... O.K., that's hyperbole - how about tens of thousands?

> The square bracket solves that problem.

Actually it didn't... my mail program still read the closing "]" as part of
the URI! Sometimes it even thinks that an ">" is a part of the URI, and
when typing them out, it sometimes includes whitespace as a part of it. I
should really get a better mail client...

--
Kindest Regards,
Sean B. Palmer
@prefix : <http://webns.net/roughterms/> .
[ :name "Sean B. Palmer" ] :hasHomepage <http://infomesh.net/sbp/> .
# or, as per Seth's suggestion:-
@prefix : [http://webns.net/roughterms/] .
[ :name "Sean B. Palmer" ] :hasHomepage [http://infomesh.net/sbp/] .
Received on Wednesday, 31 January 2001 20:33:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:51:47 GMT