Changes between Version 2 and Version 3 of Software/ContextService


Ignore:
Timestamp:
16/09/09 11:52:21 (10 years ago)
Author:
spascoe
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Software/ContextService

    v2 v3  
    2626 1. The context service API should be callable by either server-side or client-side code (AJAX).  It must be callable via: Python, JavaScript and PHP.  It must support all [http://en.wikipedia.org/wiki/Create,_read,_update_and_delete CRUD] operations through this API. 
    2727 1. The context service should be flexible enough to provide an ad-hoc session management function to aid application integration (e.g. simple key/value pair storage). 
    28  1. To support client-side calling it should support authn/authz via NdgSecurity.  This requirement is optional if we are comfortable that no private information is stored in the context.  However NdgSecurity should be used for finding the user's identity (e.g. a client application will need to get the users OpenID) 
    29  1. The context service, or a secondary service which is NdgSecurity, must provide a one-click method of adding a resource to the user's context.  This will allow MOLES catalogue records to have a "Add to Context" URL. 
     28 1. To support client-side calling it should support authn/authz via NDG Security.  This requirement is optional if we are comfortable that no private information is stored in the context.  However NDG Security should be used for finding the user's identity (e.g. a client application will need to get the users OpenID) 
     29 1. The context service, or a secondary service which is NDG Security, must provide a one-click method of adding a resource to the user's context.  This will allow MOLES catalogue records to have a "Add to Context" URL. 
    3030 
    3131== Proposed Implementation ==