Re: Uriburner, was: Interest in HTTP Problem RDF Internet Draft?

On 1 November 2015 at 19:33, Kingsley Idehen <kidehen@openlinksw.com> wrote:

> On 10/31/15 5:33 PM, Dietrich Schulten wrote:
>
> Hi Kingsley,
>
> Am 30.10.2015 15:36 schrieb Kingsley Idehen <kidehen@openlinksw.com>
> <kidehen@openlinksw.com>:
> >
> > On 10/30/15 9:19 AM, Dietrich Schulten wrote:
> >>
>
> >>
> >>
> >
> > Interesting stuff. Here are some links for tracking:
> >
> > [1]
> http://linkeddata.uriburner.com/about/id/entity/https/github.com/dret/I-D/issues
> -- Basic Entity Description Page.
> > [2] http://linkeddata.uriburner.com/c/9ULOLAX -- Deeper Faceted
> Browsing Page.
>
> What is this uriburner you are linking to every now and then? I tried to
> look around a bit but ran into a login prompt. How can it be used for
> tracking?
>
> ☺
>
> Best regards,
> Dietrich
>
>
> Hi Dietrich,
>
> URIBurner [1] is a data transformation service that creates Linked Data
> from disparate data sources. Basically, using URL patterns you end up with
> 5-Star Linked Data URIs for a variety of things.
>
> The authentication challenge you are encountering is the result of a
> service usage acl that requires some form of identification for service
> use. As you can see, it lets an agent identify itself using a variety of
> authentication protocols.
>

URI burner basically transforms the old web into a universal linked data
space, according to the original vision.  Ideally people would have done
this already by following standards, but that will take some time still.
So, while we wait, URI burner can turn much of the web into five star
linked data.


>
>
> Links:
>
> [1] http://linkeddata.uriburner.com -- URIBurner Home Page
> [2] http://linkeddata.uriburner.com/sponger_architecture.vsp#how_it_works
> - How URIBurner Works .
>
> Kingsley
>
> Am 30.10.2015 15:36 schrieb Kingsley Idehen <kidehen@openlinksw.com>
> <kidehen@openlinksw.com>:
>
> On 10/30/15 9:19 AM, Dietrich Schulten wrote:
>
> Hi,
>
> our discussion about the http-problem internet draft[1], ended with
> Markus' statement that "If [http-problem] will be widely adopted, we
> still have the luxury to be able to change Hydra".
>
> Apparently IETF has earlier pointed Melvin Carvalho to http-problem as a
> possible solution response format for an HTTP 402 Payment Required
> status code [4].
>
> Anyway, our discussion has continued off-list and finally Erik Wilde has
> started an I-D http-problem-rdf at [2]. I wanted to inform the group
> about it, in case someone is interested.
>
> The purpose of the I-D is basically the same as that of the http-problem
> draft: "This document defines a "problem
> detail" as a way to carry machine-readable details of errors in a HTTP
> response, to avoid the need to invent new error response formats for
> HTTP APIs" with the additional goal to make the semantics of the
> http-problem media types available for RDF based representations, too.
>
> Now the question: would it be OK to use the **still empty** contrib
> mailing list public-hydra-contrib@w3.org for discussions? Or would the
> group even be more comfortable if discussions took place here?
>
> Best regards,
> Dietrich
>
> [1] https://lists.w3.org/Archives/Public/public-hydra/2015Sep/0044.html
> [2] https://github.com/dret/I-D/tree/master/http-problem-rdf
> [3] https://lists.w3.org/Archives/Public/public-hydra-contrib/
> [4]https://lists.w3.org/Archives/Public/public-webpayments/2015Jun/0056.html
>
>
> Interesting stuff. Here are some links for tracking:
>
> [1]
> http://linkeddata.uriburner.com/about/id/entity/https/github.com/dret/I-D/issues
> -- Basic Entity Description Page.
> [2] http://linkeddata.uriburner.com/c/9ULOLAX -- Deeper Faceted Browsing
> Page.
>
> --
> 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
>
>
>
> --
> 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
>
>