- From: Bradley Allen <bradley.p.allen@gmail.com>
- Date: Wed, 10 Nov 2010 13:03:11 -0800
- To: nathan@webr3.org
- Cc: Linked Data community <public-lod@w3.org>
Nathan- I guess I'm not being clear about my problem. How do you get a REST API to work with fragment URIs? - BPA Bradley P. Allen http://bradleypallen.org On Wed, Nov 10, 2010 at 12:33 PM, Nathan <nathan@webr3.org> wrote: > Bradley Allen wrote: >> >> Nathan- I think you are overly discounting scalability problems with >> fragment URIs. >> >> Most of the use cases I am dealing with in moving linked data into >> production at Elsevier entail SKOS concept schemes with concepts >> numbering in the 100,000's to millions, which will be constantly under >> curation, preferably using REST APIs that allow POSTs and PUTs to >> create and update individual concepts. >> >> Can you articulate a reasonable way in which that can be accomplished >> using fragment URIs? - regards, BPA > > /resource1 > /resource2 > /resource3 > > /resource1#1 > /resource2#2 > /resource3#3 > > with the additional benefit that you can do > > /resourcea#1 > /resourcea#2 > /resourceb#1 > /resourceb#2 > > as in, exactly the same way, but with *more* options. > >
Received on Wednesday, 10 November 2010 21:03:45 UTC