 |
|
|
hi,
three things,
a question: can we consider RDDL as a lo-rest or POX based webservice?
a scenario: let us suppose we have a webservice that returns XML with
the namespace
http://www.example.com/
and this webservice is hosted at http://www.example.com with resources like
http://www.example.com/tradingexample
(note I am not just assuming GET in this URI)
what if http://www.example.com returned a rddl document, since RDDL
describes a namespace it could in a way describe the interfaces to the
service, although that the description was to the service would in
some way be indirect (this is not the right word, but I'm not sure
what word I should use to describe something like this)
a brainstorming question on the scenario above:
If the RDDL document returned links to resources external to the RDDL
site, and these resources could take methods other than GET, for
example PUT, what kind of scenarios could one concoct in such a
scenario
does all this seem like an abuse or a good use?
Cheers,
Bryan Rasmussen
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
