REST WADL file
na...@riseup.net
Boone, Keith W. (VBC NewCo non-GE)
Yes.
I would imagine you want more details.
There are a lot of different ways that you can process the server conformance statement to prepare a WADL based on the Conformance, StructureDefinition and OperationDefinitions it references.
One way you could do it would be to write several XSL templates that would transform these XML resources into WADL format.
Another way to do it would be to generate some code to handle the transformation.
Why do you need a WADL? What value does this provide that the existing resources do not?
From certain RESTful community perspectives, WADL is a bit of a “missed the boat” idea, which basically applies the same “mistakes” of SOAP to RESTful services, defeating some of the principles of REST. It was submitted as a member submission to W3C in 2009 and basically has died on the vine, with little followup.
From other perspectives, it can simplify automated code generation (i.e., Jersey).
Many FHIR API tools are doing automated code generation today from existing specification resources (e.g., Conformance, StructureDefinition, OperationDefinition, et cetera), but using custom code.
I would wonder if the value you are seeking from getting to WADL could be better invested in doing the same, or if you would be expected greater value from some of the WADL-based code and test generation applications. It would be interesting to hear more about your use case for WADL. What value do you expect to get from it?
Keith
--
You received this message because you are subscribed to the Google Groups "HAPI FHIR" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
hapi-fhir+...@googlegroups.com.
To post to this group, send email to
hapi...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/hapi-fhir/dffc778b-de35-4d6b-a186-b51a9aca82da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.