Difference between revisions of "Response to INSPIRE Network Services Architecture"
Jump to navigation
Jump to search
Wiki-JoWalsh (talk | contribs) (New page: The Network Services Architecture is not an Implementing Rule but does have a lot of impact on SDI work in Europe. The current draft '''proposes a GeoRM layer (even a null one) before all...) |
Wiki-JoWalsh (talk | contribs) m |
||
| Line 1: | Line 1: | ||
The Network Services Architecture is not an Implementing Rule but does have a lot of impact on SDI work in Europe. | The Network Services Architecture is not an Implementing Rule but does have a lot of impact on SDI work in Europe. | ||
| − | The current draft '''proposes a GeoRM layer (even a null one) before all INSPIRE services'''. | + | The current draft '''proposes a [[GeoRM]] layer (even a null one) before all INSPIRE services'''. |
It offers some arguments in favour of '''[[SOAP]] bindings for all OWS and other services''', but is actively seeking consultation from implementor/user communities ''on the usage of SOAP/WSDL in the frame of setting up an SDI.'' | It offers some arguments in favour of '''[[SOAP]] bindings for all OWS and other services''', but is actively seeking consultation from implementor/user communities ''on the usage of SOAP/WSDL in the frame of setting up an SDI.'' | ||
Revision as of 08:32, 20 December 2007
The Network Services Architecture is not an Implementing Rule but does have a lot of impact on SDI work in Europe.
The current draft proposes a GeoRM layer (even a null one) before all INSPIRE services. It offers some arguments in favour of SOAP bindings for all OWS and other services, but is actively seeking consultation from implementor/user communities on the usage of SOAP/WSDL in the frame of setting up an SDI.
The consultation ends Feb 18th 2008.