On 2/9/15 8:00 AM, Daniel Kinzler wrote:
On Mon Feb 09
2015 at 11:27:06 Daniel Kinzler <daniel.kinzler(a)wikimedia.de
><mailto:daniel.kinzler@wikimedia.de>> wrote:
>
> Am 09.02.2015 um 12:17 schrieb Magnus Manske:
> > My autodesc API serves both at the moment, so the consumer can decide
> which one
> > they want to use. Automatic descriptions can "miss the point"
sometimes,
> but are
> > generally more up-to-date.
>
> Can you post a link for us to play with?
>
>
>Interface at
>https://tools.wmflabs.org/autodesc/
>
>Example JSONFM:
>https://tools.wmflabs.org/autodesc/?q=Q3184929&lang=&mode=short&links=text&redlinks=&format=jsonfm
Thanks!
Daniel,
Have you still not considered using <link/> in <head/> of HTML docs to
enable user agents discover:
1. alternative document content sources?
2. related document content sources?
All you have to do (although you must know this already) is:
<head>
<link rel="alternate"
href="https://tools.wmflabs.org/autodesc/?q=Q3184929&lang=en&m…
title="JSON representation" />
</head>
or if you simply want to be looser:
<head>
<link rel="related"
href="https://tools.wmflabs.org/autodesc/?q=Q3184929&lang=en&m…
title="JSON representation" />
</head>
Just placing the above in your HTML aids user agents that understand HTML.
You can even go further, in regards to HTTP aware user agents (beyond
browsers) by replicating the relations above via "Link:" response metadata.
This simple tweaks solve lots of discovery related problems :)
--
Regards,
Kingsley Idehen
Founder & CEO
OpenLink Software
Company Web:
http://www.openlinksw.com
Personal Weblog 1:
http://kidehen.blogspot.com
Personal Weblog 2:
http://www.openlinksw.com/blog/~kidehen
Twitter Profile:
https://twitter.com/kidehen
Google+ Profile:
https://plus.google.com/+KingsleyIdehen/about
LinkedIn Profile:
http://www.linkedin.com/in/kidehen
Personal WebID:
http://kingsley.idehen.net/dataspace/person/kidehen#this