Re: Profiles in Linked Data

2015-05-07 Thread Mark Baker
On Thu, May 7, 2015 at 9:13 AM, Svensson, Lars l.svens...@dnb.de wrote: Mark, On Thu, May 7, 2015 at 7:05 AM, Martynas Jusevičius marty...@graphity.org wrote: On the other hand, it seems like you want different descriptions of a resource -- so it seems to me that these should in fact be

Re: URIs within URIs

2014-08-24 Thread Mark Baker
On Aug 22, 2014 12:23 PM, Ruben Verborgh ruben.verbo...@ugent.be wrote: This gets us to a deeper difference between (current) Linked Data and the rest of the Web: Linked Data uses only links as hypermedia controls, whereas the remainder of the Web uses links *and forms*. Forms are a much more

Re: Updated LOD Cloud Diagram - Missed data sources.

2014-08-15 Thread Mark Baker
On Fri, Jul 25, 2014 at 6:04 AM, Christian Bizer ch...@bizer.de wrote: Hi, But I wonder where so many other sites (including mine) went ? The problem with crawling the Web of Linked Data is really that it is hard to get the datasets on the edges that set RDF links to other sources but are

Re: Exchanging Links with LINK and UNLINK

2013-12-11 Thread Mark Baker
Link exchange over HTTP, awesome. I hope you support the 402 status code ;)

Re: representing hypermedia controls in RDF

2013-11-23 Thread Mark Baker
On Thu, Nov 21, 2013 at 1:01 PM, Markus Lanthaler markus.lantha...@gmx.net wrote: +public-hydra On Thursday, November 21, 2013 5:11 PM, Mark Baker wrote: Cool. Very similar to RDF Forms in important ways, though I think RDF Forms internalizes some useful features that Hydra could benefit from

Re: representing hypermedia controls in RDF

2013-11-21 Thread Mark Baker
On Thu, Nov 21, 2013 at 6:14 AM, Markus Lanthaler markus.lantha...@gmx.net wrote: Hi Ruben, You probably already expected me asking this :-) Why not Hydra [1]? Cool. Very similar to RDF Forms in important ways, though I think RDF Forms internalizes some useful features that Hydra could benefit

Re: Again on endpoint server limits [WAS Re: Public SPARQL endpoints:managing (mis)-use and communicating limits to users.]

2013-05-31 Thread Mark Baker
On Thu, May 30, 2013 at 10:33 AM, Kingsley Idehen kide...@openlinksw.com wrote: On 5/30/13 9:13 AM, Andrea Splendiani wrote: Hi, let me get back to this thread for two reasons. 1) I was wondering whether the report on DBPedia queries cited below was already published. 2) I have recently

Re: Content negotiation negotiation

2013-04-23 Thread Mark Baker
On Tue, Apr 23, 2013 at 1:42 PM, Hugh Glaser h...@ecs.soton.ac.uk wrote: On 22 Apr 2013, at 12:18, Phillip Lord phillip.l...@newcastle.ac.uk wrote: snip We need to check for content negotiation; I'm not clear, though, how we are supposed to know what forms of content are available. Is there

Re: SPARQL, philosophy n'stuff..

2013-04-21 Thread Mark Baker
On Fri, Apr 19, 2013 at 9:57 AM, Kingsley Idehen kide...@openlinksw.com wrote: The original query language you describe is what makes the Web, the Web. We can't just swap it out and expect the resulting architecture to still be the Web and exhibit its same desirable architectural properties.

Re: SPARQL, philosophy n'stuff..

2013-04-19 Thread Mark Baker
Kingsley, On Thu, Apr 18, 2013 at 11:21 AM, Kingsley Idehen kide...@openlinksw.com wrote: The global Web is a functional Data Space equipped with a declarative query language based on the Web's architectural essence (URIs and HTTP). It can work, and will work. The challenge is getting folks to

Re: Public SPARQL endpoints:managing (mis)-use and communicating limits to users.

2013-04-19 Thread Mark Baker
On Fri, Apr 19, 2013 at 9:25 AM, Rob Warren war...@muninn-project.org wrote: Hi Rob, There is a fundamental problem with HTTP status codes. Lets say a user submits a complex but small sparql request. My server sees the syntax is good and starts to reply in good faith. This means the server

Re: SPARQL, philosophy n'stuff..

2013-04-18 Thread Mark Baker
On Thu, Apr 18, 2013 at 10:41 AM, Barry Norton barry.nor...@ontotext.com wrote: On 18/04/2013 15:35, Jürgen Jakobitsch SWC wrote: I think the problem is that many people (especially web developers) have not yet realized that SPARQL *IS* already a REST API May I rephrase? SPARQL is already

Re: Proper usage of HTTP for LD servers, clients, crawlers etc.

2011-04-04 Thread Mark Baker
On Fri, Apr 1, 2011 at 1:44 AM, Markus Luczak-Rösch markus.luczak-roe...@fu-berlin.de wrote: Hi all! Since on the LDOW11 and USEWOD workshops at WWW there was the recent discussion about using HTTP referrers properly when browsing, crawling etc. linked data (short using it) I would like to

Re: CORS question (was Re: Proposal to assess the quality of Linked Data sources)

2011-02-25 Thread Mark Baker
On Fri, Feb 25, 2011 at 6:22 AM, Damian Steer d.st...@bristol.ac.uk wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sorry for changing the topic (and, indeed, sailing off list topic). On 24/02/11 18:28, Melvin Carvalho wrote: http://www.w3.org/wiki/CORS_Enabled [reproduced for

Re: quick advice on content negotiation

2009-12-08 Thread Mark Baker
On Tue, Dec 8, 2009 at 11:43 AM, Nathan nat...@webr3.org wrote: in addition adding the extension .n3 / .rdf to the uri causes content RDF to be returned instead. How is that information communicated to the world? Is it documented somewhere, or expressed in-band? If not the latter, then I'd

Re: [pedantic-web] Re: quick advice on content negotiation

2009-12-08 Thread Mark Baker
On Tue, Dec 8, 2009 at 12:33 PM, Nathan nat...@webr3.org wrote: actually.. how about this.. Expressing the links in HTML is fine too. GET /user/23 HTTP/1.1 Host: example.org Accept: application/rdf+xml -- HTTP/1.1 200 Ok Content-Type: application/rdf+xml Link:

Re: quick advice on content negotiation

2009-12-08 Thread Mark Baker
On Tue, Dec 8, 2009 at 12:35 PM, Kingsley Idehen kide...@openlinksw.com wrote: Nathan: see URIBurner or DBpedia responses which also include LINK response headers :-) I had no idea the community was using it. Excellent! Sequence example via cURL: kidehen$ curl -I -H Accept: text/html

Re: RDF Update Feeds + URI time travel on HTTP-level

2009-11-26 Thread Mark Baker
On Wed, Nov 25, 2009 at 6:08 PM, Michael Nelson m...@cs.odu.edu wrote: I disagree.  I would say that agent-driven negotiation is by far the most common form of conneg in use today.  Only it's not done through standardized means such as the Alternates header, but instead via language and format

Re: RDF Update Feeds + URI time travel on HTTP-level

2009-11-25 Thread Mark Baker
Michael, On Wed, Nov 25, 2009 at 1:07 AM, Michael Nelson m...@cs.odu.edu wrote: What you describe is really close to what RFC 2616 calls Agent-driven Negotiation, which is how CN exists in the absence of Accept-* request headers. That's correct. But the TCN: Choice approach is introduced as

Re: RDF Update Feeds + URI time travel on HTTP-level

2009-11-24 Thread Mark Baker
Herbert, On Tue, Nov 24, 2009 at 6:10 PM, Herbert Van de Sompel hvds...@gmail.com wrote: Just to let you know that our response to some issues re Memento raised here and on Pete Johnston's blog post (http://efoundations.typepad.com/efoundations/2009/11/memento-and-negotiating-on-time.html) is

Re: RDF Update Feeds + URI time travel on HTTP-level

2009-11-23 Thread Mark Baker
On Mon, Nov 23, 2009 at 1:01 AM, Peter Ansell ansell.pe...@gmail.com wrote: The issue with requiring people to direct requests at the URI for the Resource X at time T is that the circular linking issue I described previously comes into play because people need to pre-engineer their URI's to be

Re: RDF Update Feeds + URI time travel on HTTP-level

2009-11-22 Thread Mark Baker
Hi Chris, On Fri, Nov 20, 2009 at 1:07 PM, Chris Bizer ch...@bizer.de wrote: Hi Michael, Georgi and all, just to complete the list of proposals, here another one from Herbert Van de Sompel from the Open Archives Initiative. Memento: Time Travel for the Web http://arxiv.org/abs/0911.1112

Re: RDF Update Feeds + URI time travel on HTTP-level

2009-11-22 Thread Mark Baker
On Sun, Nov 22, 2009 at 11:59 PM, Peter Ansell ansell.pe...@gmail.com wrote: It should be up to resource creators to determine when the nature of a resource changes across time. A web architecture that requires every single edit to have a different identifier is a large hassle and likely won't