Re: Status codes / IR vs. NIR -- 303 vs. 200

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 20:34:14 UTC