Document Actions
Registry API
This is the list of functions that will be available on the registry.
Issues
(also note any issues that are listed with each of the functions)1. Is the use of a URI the best way to identify a service?
IR and DM
To remain working with the CIMA structure the registry will define the following functions. Each Parcel is an XML object that then gets processed by the registry.1. receiveParcel
Arguments: parcel
Returns: null
2. receiveParcelRR
Arguments: parcel
Returns: String
Portal
1. getServices
Gets a list of services that are associated with the user's credentials and groups. These requests would also be forwarded by the National Registry.
Arguments: certificate, groups
Returns: service list (sensor URI, sensor names and sensor IDs)
Issues: is the certificate and group information linked in one object?
2. getNewServices
Gets a list of services that have been registered but yet to be accepted into the dimsim instance.
Arguments: null
Returns: service list (sensor URI and owner info)
3. addUser
Add a user for use of a service.
Arguments: service URI, username, isAdmin
Returns: user ID
Issues: is there anything else here that needs to be known about the user?
5. removeUser
Remove a user from use of a service.
Arguments: service URI, user ID
Returns: boolean
6. addGroup
Add a group for use of a service
Arguments: service URI, groupname
Returns: group ID
Issues: is there anything else here that needs to be knonw about the group?
7. removeGroup
Removes a group from use of a service.
Arguments: service URI, group ID
Returns: boolean
8. getSensorML
Get the sensorML doc for a sensor
Arguments: service URI, sensor ID
Returns: SensorML doc
Forgot your password?
