api4kb_persistent_storage
====== Differences ====== This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
api4kb_persistent_storage [2013/03/17 15:54] rmbell |
api4kb_persistent_storage [2013/03/17 16:12] (current) rmbell |
||
|---|---|---|---|
| Line 35: | Line 35: | ||
| CreateKB( | CreateKB( | ||
| - | in URI/URL knowledgeBase, - the desired URI to associate to the (new) KB | + | in URI/URL knowledgeBase, : the desired URI to associate to the (new) KB |
| - | out URL/URI effectiveKnowledgeBaseURI - the URI assigned to the (new) KB | + | out URL/URI effectiveKnowledgeBaseURI : the URI assigned to the (new) KB |
| ); | ); | ||
| Post-condition : Ensures that a knowledgeBase exists for the given URI (at the given URL??) | Post-condition : Ensures that a knowledgeBase exists for the given URI (at the given URL??) | ||
| + | |||
| REST mapping : POST | REST mapping : POST | ||
| Creates a new knowledge base and associates it to the given URI. If the knowledge base already exists, its URI is returned. | Creates a new knowledge base and associates it to the given URI. If the knowledge base already exists, its URI is returned. | ||
| + | |||
| TODO: discuss the use of URIs vs URLs | TODO: discuss the use of URIs vs URLs | ||
| Line 65: | Line 67: | ||
| ---- | ---- | ||
| - | UpdateResourceInKB( in URL knowledgeBase, | + | UpdateResourceInKB( |
| + | in URL knowledgeBase, | ||
| in URI resourceId, | in URI resourceId, | ||
| in URL resourceLocation, | in URL resourceLocation, | ||
| Line 73: | Line 76: | ||
| REST mapping : POST | REST mapping : POST | ||
| - | TODO. This method should be defined. What is the exact semantics of updating a resource in a KB, as opposed to setting it? It could be interpreted in terms of versioning? Or the "old" and "new" resources should be "merged" (whatever that means)? | + | TODO: This method should be defined. What is the exact semantics of updating a resource in a KB, as opposed to setting it? It could be interpreted in terms of versioning? Or the "old" and "new" resources should be "merged" (whatever that means)? |
| Line 86: | Line 89: | ||
| Post-condition : The KB is not altered | Post-condition : The KB is not altered | ||
| + | |||
| REST mapping : GET | REST mapping : GET | ||
| Line 103: | Line 107: | ||
| Pre-condition : the KB contains the resource mapped by resourceID. The client must have the appropriate rights to write at exportLocation. | Pre-condition : the KB contains the resource mapped by resourceID. The client must have the appropriate rights to write at exportLocation. | ||
| + | |||
| Integrity : the format specified by resourceDescriptor is compatible with the nature of the resource | Integrity : the format specified by resourceDescriptor is compatible with the nature of the resource | ||
| + | |||
| Post-condition : the exportLocation will contain a serialized copy of the resource mapped by resourceId, as defined by resourceDescriptor. The KB is not altered. | Post-condition : the exportLocation will contain a serialized copy of the resource mapped by resourceId, as defined by resourceDescriptor. The KB is not altered. | ||
| + | |||
| REST mapping : POST | REST mapping : POST | ||
| Line 117: | Line 124: | ||
| in URI resourceId, : the URI of the resource to be deleted | in URI resourceId, : the URI of the resource to be deleted | ||
| out TODO ); | out TODO ); | ||
| + | |||
| Pre-condition : the KB contains a resource mapping for resourceID ??? | Pre-condition : the KB contains a resource mapping for resourceID ??? | ||
| + | |||
| Post-condition : the KB no longer contains a resource mapping for resourceID | Post-condition : the KB no longer contains a resource mapping for resourceID | ||
| + | |||
| REST mapping : DELETE | REST mapping : DELETE | ||
api4kb_persistent_storage.1363550060.txt.gz · Last modified: 2013/03/17 15:54 by rmbell
Page Tools
