- From: Henry Story <henry.story@bblfish.net>
- Date: Thu, 29 Nov 2012 00:26:29 +0100
- To: Henry Story <henry.story@bblfish.net>
- Cc: Ted Thibodeau Jr <tthibodeau@openlinksw.com>, Jόrgen Jakobitsch <j.jakobitsch@semantic-web.at>, WebID Group <public-webid@w3.org>, nathan <nathan@webr3.org>
- Message-Id: <9B8621EF-4077-4BFA-9334-2EB7EF3C66DA@bblfish.net>
On 28 Nov 2012, at 23:59, Henry Story <henry.story@bblfish.net> wrote:
>
> On 28 Nov 2012, at 21:25, Ted Thibodeau Jr <tthibodeau@openlinksw.com> wrote:
>
>> All --
>>
>> A potentially interesting bit here, since one of the major
>> points of all this discussion is interoperability of tools
>> and the power of follow-your-nose...
>>
>>
>> On Nov 24, 2012, at 05:52 AM, Henry Story wrote:
>>
>>> - http://xmlns.com/foaf/0.1/knows
>>> - http://xmlns.com/foaf/0.1/mbox
>>> - http://xmlns.com/foaf/0.1/Person
>>> - http://xmlns.com/foaf/0.1/Agent
>>
>> The above all look right in my Mail.app, and I can click any
>> of them and get redirected to <http://xmlns.com/foaf/spec/>.
>>
>> (
>> Tangentially, this redirection seems overly broad.
>>
>> Remembering that 303s can be applied to the document portion
>> of a URI, but cannot take the fragment ID into account [while
>> 303 *targets* *can* include a fragment ID.], I would expect
>> the first URI above to redirect to either
>> <http://xmlns.com/foaf/spec/#knows> or
>> <http://xmlns.com/foaf/spec/knows> [which could then
>> redirect again to <http://xmlns.com/foaf/spec/#knows>] ...
>> and actually, I'd expect the generic /spec/ to redirect to
>> a specifically versioned target, not the other way around...
>> )
>>
>>
>>
>> But the following, which Henry initially seemed to be
>> suggesting as better (though his conclusion seems otherwise)?
>>
>>> - http://xmlns.com/foaf/0.1/knows#
>>> - http://xmlns.com/foaf/0.1/mbox#
>>> - http://xmlns.com/foaf/0.1/Person#
>>> - http://xmlns.com/foaf/0.1/Agent#
>>
>> These URIs don't look right in Mail.app.
>>
>> The URI highlighting stops at the last solidus ("/"), so
>> they all look like links to the same page --
>> <http://xmlns.com/foaf/0.1/> -- and that is where clicking
>> them takes me.
>
> Does the following work better? I had perhaps wrongly used a unicode character
> right after the # .
>
> - http://xmlns.com/foaf/0.1/knows#it
> - http://xmlns.com/foaf/0.1/mbox#it
> - http://xmlns.com/foaf/0.1/Person#it
> - http://xmlns.com/foaf/0.1/Agent#it
Mhh. No they don't as each of them redirect to the
same URI it seems:
http://xmlns.com/foaf/spec/#it
$ curl -I http://xmlns.com/foaf/0.1/knows
HTTP/1.1 303 See Other
Date: Wed, 28 Nov 2012 23:23:34 GMT
Server: Apache/2.2.14 (Ubuntu)
Access-Control-Allow-Origin: *
Location: http://xmlns.com/foaf/spec/
Vary: Accept-Encoding
Content-Type: text/html; charset=iso-8859-1
That seems unfortunate.
>
>
>
>>
>> (I am then redirected to the same <http://xmlns.com/foaf/spec/>
>> as above -- but again, if the redirections were handled as
>> I suggest above, this end result would be very wrong.)
>>
>> Be seeing you,
>>
>> Ted
>>
>>
>>
>> --
>> A: Yes. http://www.guckes.net/faq/attribution.html
>> | Q: Are you sure?
>> | | A: Because it reverses the logical flow of conversation.
>> | | | Q: Why is top posting frowned upon?
>>
>> Ted Thibodeau, Jr. // voice +1-781-273-0900 x32
>> Senior Support & Evangelism // mailto:tthibodeau@openlinksw.com
>> // http://twitter.com/TallTed
>> OpenLink Software, Inc. // http://www.openlinksw.com/
>> 10 Burlington Mall Road, Suite 265, Burlington MA 01803
>> Weblog -- http://www.openlinksw.com/blogs/
>> LinkedIn -- http://www.linkedin.com/company/openlink-software/
>> Twitter -- http://twitter.com/OpenLink
>> Google+ -- http://plus.google.com/100570109519069333827/
>> Facebook -- http://www.facebook.com/OpenLinkSoftware
>> Universal Data Access, Integration, and Management Technology Providers
>>
>>
>>
>>
>>
>>
>>
>
> Social Web Architect
> http://bblfish.net/
>
Social Web Architect
http://bblfish.net/
Attachments
- application/pkcs7-signature attachment: smime.p7s
Received on Wednesday, 28 November 2012 23:27:06 UTC