On 15/03/12 20:20, Andy Seaborne wrote:
Ah - OK - The problem is that /dataset is both a special name (the name
of an action that sets the session state to indicate the dataset) and in
this setup the name of the dataset. For any dataset DA, /DA is routed to
the graph store protocol in expectation that the dataset URI is also the
graph store protocol service URI.
This only affects a dataset called "/dataset", only if using the UI forms.
What do you think the important case is? Let's design for that and fit
other names around it. One possibility is that all service URIs start $
or "_" or even "/$/"
There's a touch of HTTP irony here.
/control-panel.tpl is a POST to /dataset
The POST responds by setting a session attribute
and redirecting to sparql.tpl using an HTTP 303. This is the original,
before-semantic-web use of 303.
Getting rid of the /control-panel.tpl page is one possibility if anyone
has any design ideas - I had an idea to put management functions
(backup, create database etc etc) on that page later but in the end, the
management actions (not that there are many yet) are on a different
port, which helps security and keeps the dataset namespace clean.
Andy
