Skip to:
Intended to be used with URL rewriting in a web server; to be able to host "foreign" URIs in the local system.
Possibility 1 (global):
GET /store/resource/{resource-uri}GET /store/metadata/{resource-uri}
Possibility 2 (global):
GET /store/by-uri/{resource-uri}?entity=[resource|metadata]
Possibility 3 (context-specific):
GET /store/{context-id}/by-uri/{resource-uri}?entity=[resource|metadata]
Possibility 4 (context-specific):
GET /store/{context-id}/resource/by-uri/{resource-uri}GET /store/{context-id}/metadata/by-uri/{resource-uri}
Possibility 5 (context-specific):
GET /store/{context-id}/resource/by-uri?uri={resource-uri}GET /store/{context-id}/metadata/by-uri?uri={resource-uri}
Possibility 6 (global or context-specific):
GET /store/[{context-id}]/lookup?uri={resource-uri}&entity=[resource|metadata]
Only support for metadata necessary for now
Also documented in the wiki: https://code.google.com/p/entrystore/wiki/KnowledgeBaseLookup
Intended to be used with URL rewriting in a web server; to be able to host "foreign" URIs in the local system.
Possibility 1 (global):
GET /store/resource/{resource-uri}
GET /store/metadata/{resource-uri}
Possibility 2 (global):
GET /store/by-uri/{resource-uri}?entity=[resource|metadata]
Possibility 3 (context-specific):
GET /store/{context-id}/by-uri/{resource-uri}?entity=[resource|metadata]
Possibility 4 (context-specific):
GET /store/{context-id}/resource/by-uri/{resource-uri}
GET /store/{context-id}/metadata/by-uri/{resource-uri}
Possibility 5 (context-specific):
GET /store/{context-id}/resource/by-uri?uri={resource-uri}
GET /store/{context-id}/metadata/by-uri?uri={resource-uri}
Possibility 6 (global or context-specific):
GET /store/[{context-id}]/lookup?uri={resource-uri}&entity=[resource|metadata]