Hi Kingsley! Earlier I forwarded Eran's pointer to the Apache Clerezza list, thinking this was very much in scope for semweb/Linked Data projects, the fact that OpenLink's on board validates that thought.
Do you happen to know of any surveys of techniques for site metadata - robots.txt, WebFinger to infinity and beyond? Cheers, Danny. On 25 May 2011 14:39, Kingsley Idehen <[email protected]> wrote: > On 5/25/11 5:29 AM, Paul Lindner wrote: > > Seems fine to me. > I will be implementing this in shindig in the near future.. > > Likewise, we've long supported this at OpenLink Software in our Virtuoso > product re. Linked Data Deployment. Here is an excerpt from a mail I sent to > the Linked Open Data (LOD) mailing about this discovery pattern for metadata > scoped to the DBpedia URI host: > > 1. http://dbpedia.org/.well-known/host-meta -- discover URI template > patterns for an given data space (URI host) > > 2. http://dbpedia.org/describe/?uri=http://dbpedia.org/resource/Paris -- > end-user oriented URL that's bookmark friendly and hack-able for a document > about 'Paris' > > 3. http://dbpedia.org/resource/Paris --- actual URI based Entity Name that's > confined to @href of relevant portion of "About: Paris" anchor text > > 4. http://dbpedia.org/data/Paris.n3 -- discovered by footer links (human), > <link/> (web 1.0 or 2.0 developer), or "Link:" header responses > > 5. http://dbpedia.org/data/Paris.rdf -- ditto > > 6. http://dbpedia.org/data/Paris.ntriples (will be .nt soon) -- ditto. > > > Kingsley > > > On Mon, May 9, 2011 at 1:05 PM, Eran Hammer-Lahav <[email protected]> > wrote: >> >> (Please discuss this draft on the Apps-Discuss <[email protected]> >> mailing list) >> >> http://tools.ietf.org/html/draft-hammer-hostmeta-15 >> >> After letting -13 expire with little to no interest, I have been asked to >> get this work done and published. Given that this draft if the only actual >> WebFinger specification, I figured I'd give this group the heads up that I >> plan to ask for another IETF Last Call this week and be done with it. >> Changes since -13 (last one discussed here): >> * Reworked HTTP vs HTTPS language moving the decision which to use to the >> application using host-meta. So if you are writing a protocol using it, you >> need to decide how to handle it, which to support, and which to ask for >> first. >> * Added JRD format as an appendix. This format is different from the JRD >> previously published on my blog. The main change is keeping the order of >> links exactly the same as in the XML document. >> If you at all care about this work, please review it now. Otherwise, it >> will be published as-is. >> EHL > > > -- > > Regards, > > Kingsley Idehen > President & CEO > OpenLink Software > Web: http://www.openlinksw.com > Weblog: http://www.openlinksw.com/blog/~kidehen > Twitter/Identi.ca: kidehen > > > > > -- http://danny.ayers.name
