Modernisation of protocols - improve compatability with modern web dev tools GDF: Still very interested in modern definition of protocols/APIs (e..g JSON/
OpenAPI) to assist service implementors to use modern tools. High priority for Rubin
FB: How would that look like
GDF: Way more services than clients - clients have resources to stay up to date - would need to update clients to support new services while supporting old services. New services would be json based
GDF: Suggest a tiger team as no one service can do this alone
GM: Have used microsservices with json to send votable in the new SIMBAD's
ConeSearch service
GDF: About service interaction not votable format change - so how UWS works. Really hard to implement UWS in contemporary
Tim: Is there support for json? Yes, then presumably some would be intersted in volunteering.
RE: NED already has json behind the scenes and easier to convert json
DM: Suggest updating standards as defining the data model and then have an examples of the json implementation as well as XML. Don't want to be talking in 10 years about how to convert away from json!
Joshua Fraustro: MAST has a model of the UWS interactions - need management approval to make them open source and share.
Tim: Use Pydantic and
FastAPI too - very happy with them