-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Vikash, here goes the first try for a user story:
User finds a new service / creates a new service and wants to publish it. All that is needed to register a new service is a user name (authentication) with email for confirmation, the Capabilities URL of the service and whether it should be public. Q: What happens if this URL (or a similar one?) has already been uploaded earlier? Add a counter for the the same URL (uploaded several times)? A: The Capabilities URL needs to be checked against the ones already in the database. -> What happens then? Q: What happens if the user gets "lost", is deleted, etc.? A: ? Q: What happens if the service is deleted by another user? (This is currently not possible, it would generate an error message). Q: What happens if Mapbender cannot read the capabilities document? A: Error message & ? Q: Are we going to use this "interface" also to update services or do we need to create another one? A: ? We add these User Stories to the Wiki so that we can refine them there: http://www.mapbender.org/Talk:RESTful_API Best regads, Arnulf. - -- Nothing makes sense, except we make it. http://www.metaspatial.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwFO7kACgkQXmFKW+BJ1b1FxwCfeCyznkireorNnhg4/Kr4iMHR 4FIAn1BfYIzXmsl2LLWSV36kFejKmgpM =4NBN -----END PGP SIGNATURE----- _______________________________________________ Mapbender_dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapbender_dev
