Had forgotten to mention: - There needs to be a simpler way to get concept answers. Currently it is lengthy and since this is an operation that is done very often should be an array that represents the full concept and provides links to all the concept answers if the concept is of question type or is a set or is a coded concept
--- Regards, Saptarshi PURKAYASTHA My Tech Blog: http://sunnytalkstech.blogspot.com You Live by CHOICE, Not by CHANCE On 11 February 2012 02:42, Saptarshi Purkayastha <[email protected]> wrote: > Following are some of my comments: > > Good parts: > - XML default for browser and JSON for JavaScript is perfect. Accept-type > response is perfectly logical and standard > - the 3 representations are nice and helps reduce load > - the simple ?q= search is easy > - POST is good for both doing update and create > >> >> - Does the web service API give you access to the functionality you >> need? >> >> - Provider and Order is missing although there is links to orders from > Encounter and Obs. This is important since the OPD modules create orders to > lab and pharmacy among other modules. > - ComplexObs (images/videos) are not exposed as Base64 encoded string > - Other authentication ways (more than just currently supported Basic) > required. This is a problem where sending headers from cross-domain is a > challenge. > - Double is default and Float is not supported > - Form or FormSchema is also useful to be exposed ** (may be v1.1) > >> >> - Does it behave the way you want and expect it to? >> >> - representation and query cannot be done simultaneously. i.e > ?q=John&v=full should be possible, but currently doesn't work. This is > expected since we should be able to pass whatever combination of parameters. > - DELETE using the !purge is difficult to understand. > >> >> - Were you able to get up and running relatively quickly, with the >> existing documentation? >> >> - Documentation needs to be improved to be more descriptive of how to > understand each of the different properties of the resources > - More examples are needed > - Needs a WADL instead of just a catalog that returns a JSON. This will > give links to resources that are refs pointing to other resources > >> >> - Does the API look like what you'd like us to release as "1.0", and >> support in the long run? >> >> If above issues are covered then its a good 1.0 release. > We also need important modules to start exposing REST services. This means > bundled modules/important modules also need to be supported in long run > > --- > Regards, > Saptarshi PURKAYASTHA > > > My Tech Blog: http://sunnytalkstech.blogspot.com > You Live by CHOICE, Not by CHANCE > _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
