Web Services Standard

[GoogleCodeExporter]

Need to move the I&R industry to a web services standard which is the best way 
to facilitate real-time possibilities. 

Original issue reported on code.google.com by edward.p...@gmail.com on 21 Jun 2011 at 4:55

[GoogleCodeExporter]

There needs to be a web services
standard that all vendors can use to
develop around. The standard needs
to outline where data is placed and
how it should be stored.

Original comment by edward.p...@gmail.com on 21 Jun 2011 at 5:02

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This likely could be built upon the (updated) AIRS XML standard. To be 
scalable, it seems it ought to be a centralized "messaging hub" to which I&R 
software instances can "subscribe" to changes on a permission basis with their 
specific partner agencies.

The goal is that AIRS XML exporting/importing/transferring of files need not 
occur so databases can be kept in synch in realtime via web services. Such a 
messaging hub would be ideal for ensuring the updates are performed in the 
right sequence, that they are asynchronous, and scalable (so a myriad of 
point-to-point connections are not required).

Original comment by bleeb...@gmail.com on 9 Dec 2011 at 7:20

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Again, this does not seem appropriate to try to include in the Schema itself.  
In general, though, we agree that working with Web Services to facilitate 
specific business needs related to data exchange would be useful.  But, it 
doesn't seem appropriate for our task at hand.  Several other issues already 
noted to reduce file size, etc will help with this type of data exchange.

Original comment by gglbwmn2...@gmail.com on 18 Jan 2012 at 5:15

[GoogleCodeExporter]

Voted for implementation, and in 4.0 release.

Original comment by e...@ejahn.net on 18 Feb 2012 at 3:06

• Changed state: Accepted

[eric-jahn]

This will be implemented in the forthcoming JSON API.