graphstore questions

hi,

in preparation for my implementation of an ld-platform
i'm starting off with the easier graphstore [1] (also because i can
reuse a couple of things) but have a couple of questions.

1. is there a better mailing list to write to?
2. is this [2] the official test suite for the graphstore or is there a
newer version? if yes, there's an error in the test-suite 
(compare "PUT - Initial state" and "PUT - mismatched payload", i don't
see a difference)
3. graph-document-resource-entity mashup. 
   a) from the example is the spec [3] and the sample sparql query over 
   there i judge that the graph url param is meant to denote a graph-uri
   (the quad part).
   b) from here [4] i judge that the graph url param can also denote a 
   resource (URI-R)
   c) and from the tests here [5] i judge that the graph url param 
   denotes a document url (see "GET of PUT - Initial state").

   => <http://www.turnguard.com/turnguard> a foaf:ConfusedPerson .

  maybe i just was missing when this was covered in school so please 
  excuse my ignorance but i need to clearify this for once and for all 
  (and maybe someone else also sees the light).
  we had the discussion with resource/entity which led me to skip the
  the term "resource" entirely, my best practice is to talk about 
  entities and documents (entity-URI and document-URL respectivly)

  - does "resource" mean "document" in the first place?
    (so that "URI-R" [4] equals "document-URL" returns true)
  - can the graph url param denote an entity-URI? if that's not
    allowed then this should be noted somewhere (bold) along whith a 
    http status code for the response. if it is allowed than the 
    graph url param can really be a graph (quad), entity-URI or 
    document-URL (resource [see above]) => no good.
  - is there a hidden requirement/best practice to put documents
    in a graph (the quad part) of the same name? 

  it might be a good idea to unify these terms across all linked data 
  working groups.

  any comment really appreciated
  wkr jürgen

[1] http://www.w3.org/TR/sparql11-http-rdf-update
[2]
http://www.w3.org/2009/sparql/docs/tests/data-sparql11/http-rdf-update/
[3] http://www.w3.org/TR/sparql11-http-rdf-update/#http-put
[4] http://www.w3.org/2012/ldp/wiki/Linked_Data_Platform_%28LDP%
29_vs_SPARQL_Graph_Store_HTTP_Protocol_%28GSP%29
[5]
http://www.w3.org/2009/sparql/docs/tests/data-sparql11/http-rdf-update/#put__graph_already_in_store


-- 
| Jürgen Jakobitsch, 
| Software Developer
| Semantic Web Company GmbH
| Mariahilfer Straße 70 / Neubaugasse 1, Top 8
| A - 1070 Wien, Austria
| Mob +43 676 62 12 710 | Fax +43.1.402 12 35 - 22

COMPANY INFORMATION
| web       : http://www.semantic-web.at/
| foaf      : http://company.semantic-web.at/person/juergen_jakobitsch
PERSONAL INFORMATION
| web       : http://www.turnguard.com
| foaf      : http://www.turnguard.com/turnguard
| g+        : https://plus.google.com/111233759991616358206/posts
| skype     : jakobitsch-punkt
| xmlns:tg  = "http://www.turnguard.com/turnguard#"

Received on Tuesday, 10 September 2013 08:22:23 UTC