Difference: DALGWSTigerTeam (1 vs. 32)

Revision 322024-05-22 - JamesDempsey

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Deleted:
<
<
 

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

  1. 22 Jan 2024 at 20:00 UTC - yopad shared notes - IVOA_22Jan_PTTT.pdf
  2. 26 Feb 2024 at 20:00 UTC - yopad shared notes (will expire April 2024) - IVOA_26Feb_PTTT.pdf
  3. Mon 25 Mar 2024 20:00 UTC - yopad shared notes (will expire May 2024) - IVOA_26Mar_PTTT.pdf
  4. Mon 22 Apr 2024 20:00 UTC - yopad shared notes (will expire June 2024) - IVOA_26Apr_PTTT.pdf
  5. Thu/Fri May 16/17 Sydney 10am Local time;
    1. Agenda - PTTT_May1617_Schedule.pdf
    2. Notes - Yopad shared notes May 16, Yopad shared notes May 17 (will expired July 2024) - IVOA_16May_PTTT.pdf and IVOA_17May_PTTT.pdf
Added:
>
>
  1. Wed 22 May 2024 at 9am Sydney - P3T Plenary session
 

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

META FILEATTACHMENT attachment="IVOA_22Jan_PTTT.pdf" attr="" comment="" date="1707955225" name="IVOA_22Jan_PTTT.pdf" path="IVOA_22Jan_PTTT.pdf" size="40242" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Feb_PTTT.pdf" attr="" comment="" date="1709843589" name="IVOA_26Feb_PTTT.pdf" path="IVOA_26Feb_PTTT.pdf" size="51556" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Mar_PTTT.pdf" attr="" comment="" date="1712057496" name="IVOA_26Mar_PTTT.pdf" path="IVOA_26Mar_PTTT.pdf" size="49847" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Apr_PTTT.pdf" attr="" comment="" date="1715070579" name="IVOA_26Apr_PTTT.pdf" path="IVOA_26Apr_PTTT.pdf" size="41597" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="PTTT_May1617_Schedule.pdf" attr="" comment="PTTT Face to Face schedule - May 16/17" date="1715809026" name="PTTT_May1617_Schedule.pdf" path="PTTT_May1617_Schedule.pdf" size="55725" user="JanetEvans" version="1"
META FILEATTACHMENT attachment="IVOA_16May_PTTT.pdf" attr="" comment="" date="1716094949" name="IVOA_16May_PTTT.pdf" path="IVOA_16May_PTTT.pdf" size="56261" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_17May_PTTT.pdf" attr="" comment="" date="1716094980" name="IVOA_17May_PTTT.pdf" path="IVOA_17May_PTTT.pdf" size="57019" user="JamesDempsey" version="1"

Revision 312024-05-22 - TimJenness

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Changed:
<
<
>
>
 

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

  1. 22 Jan 2024 at 20:00 UTC - yopad shared notes - IVOA_22Jan_PTTT.pdf
  2. 26 Feb 2024 at 20:00 UTC - yopad shared notes (will expire April 2024) - IVOA_26Feb_PTTT.pdf
  3. Mon 25 Mar 2024 20:00 UTC - yopad shared notes (will expire May 2024) - IVOA_26Mar_PTTT.pdf
  4. Mon 22 Apr 2024 20:00 UTC - yopad shared notes (will expire June 2024) - IVOA_26Apr_PTTT.pdf
  5. Thu/Fri May 16/17 Sydney 10am Local time;
Changed:
<
<
    1. Agenda - PTTT_May1617_Schedule.pdf
>
>
    1. Agenda - PTTT_May1617_Schedule.pdf
 
    1. Notes - Yopad shared notes May 16, Yopad shared notes May 17 (will expired July 2024) - IVOA_16May_PTTT.pdf and IVOA_17May_PTTT.pdf

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

META FILEATTACHMENT attachment="IVOA_22Jan_PTTT.pdf" attr="" comment="" date="1707955225" name="IVOA_22Jan_PTTT.pdf" path="IVOA_22Jan_PTTT.pdf" size="40242" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Feb_PTTT.pdf" attr="" comment="" date="1709843589" name="IVOA_26Feb_PTTT.pdf" path="IVOA_26Feb_PTTT.pdf" size="51556" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Mar_PTTT.pdf" attr="" comment="" date="1712057496" name="IVOA_26Mar_PTTT.pdf" path="IVOA_26Mar_PTTT.pdf" size="49847" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Apr_PTTT.pdf" attr="" comment="" date="1715070579" name="IVOA_26Apr_PTTT.pdf" path="IVOA_26Apr_PTTT.pdf" size="41597" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="PTTT_May1617_Schedule.pdf" attr="" comment="PTTT Face to Face schedule - May 16/17" date="1715809026" name="PTTT_May1617_Schedule.pdf" path="PTTT_May1617_Schedule.pdf" size="55725" user="JanetEvans" version="1"
META FILEATTACHMENT attachment="IVOA_16May_PTTT.pdf" attr="" comment="" date="1716094949" name="IVOA_16May_PTTT.pdf" path="IVOA_16May_PTTT.pdf" size="56261" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_17May_PTTT.pdf" attr="" comment="" date="1716094980" name="IVOA_17May_PTTT.pdf" path="IVOA_17May_PTTT.pdf" size="57019" user="JamesDempsey" version="1"

Revision 302024-05-19 - JamesDempsey

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

  1. 22 Jan 2024 at 20:00 UTC - yopad shared notes - IVOA_22Jan_PTTT.pdf
  2. 26 Feb 2024 at 20:00 UTC - yopad shared notes (will expire April 2024) - IVOA_26Feb_PTTT.pdf
  3. Mon 25 Mar 2024 20:00 UTC - yopad shared notes (will expire May 2024) - IVOA_26Mar_PTTT.pdf
  4. Mon 22 Apr 2024 20:00 UTC - yopad shared notes (will expire June 2024) - IVOA_26Apr_PTTT.pdf
Changed:
<
<
  1. Thu/Fri May 16/17 Sydney 10am Local time; Agenda - PTTT_May1617_Schedule.pdf - yopad shared notes: May 16, May 17
>
>
  1. Thu/Fri May 16/17 Sydney 10am Local time;
Added:
>
>
    1. Agenda - PTTT_May1617_Schedule.pdf
    2. Notes - Yopad shared notes May 16, Yopad shared notes May 17 (will expired July 2024) - IVOA_16May_PTTT.pdf and IVOA_17May_PTTT.pdf
 

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

META FILEATTACHMENT attachment="IVOA_22Jan_PTTT.pdf" attr="" comment="" date="1707955225" name="IVOA_22Jan_PTTT.pdf" path="IVOA_22Jan_PTTT.pdf" size="40242" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Feb_PTTT.pdf" attr="" comment="" date="1709843589" name="IVOA_26Feb_PTTT.pdf" path="IVOA_26Feb_PTTT.pdf" size="51556" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Mar_PTTT.pdf" attr="" comment="" date="1712057496" name="IVOA_26Mar_PTTT.pdf" path="IVOA_26Mar_PTTT.pdf" size="49847" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Apr_PTTT.pdf" attr="" comment="" date="1715070579" name="IVOA_26Apr_PTTT.pdf" path="IVOA_26Apr_PTTT.pdf" size="41597" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="PTTT_May1617_Schedule.pdf" attr="" comment="PTTT Face to Face schedule - May 16/17" date="1715809026" name="PTTT_May1617_Schedule.pdf" path="PTTT_May1617_Schedule.pdf" size="55725" user="JanetEvans" version="1"
Added:
>
>
META FILEATTACHMENT attachment="IVOA_16May_PTTT.pdf" attr="" comment="" date="1716094949" name="IVOA_16May_PTTT.pdf" path="IVOA_16May_PTTT.pdf" size="56261" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_17May_PTTT.pdf" attr="" comment="" date="1716094980" name="IVOA_17May_PTTT.pdf" path="IVOA_17May_PTTT.pdf" size="57019" user="JamesDempsey" version="1"
 

Revision 292024-05-16 - MarcoMolinaro

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

  1. 22 Jan 2024 at 20:00 UTC - yopad shared notes - IVOA_22Jan_PTTT.pdf
  2. 26 Feb 2024 at 20:00 UTC - yopad shared notes (will expire April 2024) - IVOA_26Feb_PTTT.pdf
  3. Mon 25 Mar 2024 20:00 UTC - yopad shared notes (will expire May 2024) - IVOA_26Mar_PTTT.pdf
  4. Mon 22 Apr 2024 20:00 UTC - yopad shared notes (will expire June 2024) - IVOA_26Apr_PTTT.pdf
Changed:
<
<
  1. Thu/Fri May 16/17 Sydney 10am Local time; Agenda - PTTT_May1617_Schedule.pdf - yopad shared notes
>
>
  1. Thu/Fri May 16/17 Sydney 10am Local time; Agenda - PTTT_May1617_Schedule.pdf - yopad shared notes: May 16, May 17
 

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

META FILEATTACHMENT attachment="IVOA_22Jan_PTTT.pdf" attr="" comment="" date="1707955225" name="IVOA_22Jan_PTTT.pdf" path="IVOA_22Jan_PTTT.pdf" size="40242" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Feb_PTTT.pdf" attr="" comment="" date="1709843589" name="IVOA_26Feb_PTTT.pdf" path="IVOA_26Feb_PTTT.pdf" size="51556" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Mar_PTTT.pdf" attr="" comment="" date="1712057496" name="IVOA_26Mar_PTTT.pdf" path="IVOA_26Mar_PTTT.pdf" size="49847" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Apr_PTTT.pdf" attr="" comment="" date="1715070579" name="IVOA_26Apr_PTTT.pdf" path="IVOA_26Apr_PTTT.pdf" size="41597" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="PTTT_May1617_Schedule.pdf" attr="" comment="PTTT Face to Face schedule - May 16/17" date="1715809026" name="PTTT_May1617_Schedule.pdf" path="PTTT_May1617_Schedule.pdf" size="55725" user="JanetEvans" version="1"

Revision 282024-05-16 - JanetEvans

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Added:
>
>
 

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

  1. 22 Jan 2024 at 20:00 UTC - yopad shared notes - IVOA_22Jan_PTTT.pdf
  2. 26 Feb 2024 at 20:00 UTC - yopad shared notes (will expire April 2024) - IVOA_26Feb_PTTT.pdf
  3. Mon 25 Mar 2024 20:00 UTC - yopad shared notes (will expire May 2024) - IVOA_26Mar_PTTT.pdf
  4. Mon 22 Apr 2024 20:00 UTC - yopad shared notes (will expire June 2024) - IVOA_26Apr_PTTT.pdf
  5. Thu/Fri May 16/17 Sydney 10am Local time; Agenda - PTTT_May1617_Schedule.pdf - yopad shared notes

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

META FILEATTACHMENT attachment="IVOA_22Jan_PTTT.pdf" attr="" comment="" date="1707955225" name="IVOA_22Jan_PTTT.pdf" path="IVOA_22Jan_PTTT.pdf" size="40242" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Feb_PTTT.pdf" attr="" comment="" date="1709843589" name="IVOA_26Feb_PTTT.pdf" path="IVOA_26Feb_PTTT.pdf" size="51556" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Mar_PTTT.pdf" attr="" comment="" date="1712057496" name="IVOA_26Mar_PTTT.pdf" path="IVOA_26Mar_PTTT.pdf" size="49847" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Apr_PTTT.pdf" attr="" comment="" date="1715070579" name="IVOA_26Apr_PTTT.pdf" path="IVOA_26Apr_PTTT.pdf" size="41597" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="PTTT_May1617_Schedule.pdf" attr="" comment="PTTT Face to Face schedule - May 16/17" date="1715809026" name="PTTT_May1617_Schedule.pdf" path="PTTT_May1617_Schedule.pdf" size="55725" user="JanetEvans" version="1"

Revision 272024-05-16 - JamesDempsey

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

  1. 22 Jan 2024 at 20:00 UTC - yopad shared notes - IVOA_22Jan_PTTT.pdf
  2. 26 Feb 2024 at 20:00 UTC - yopad shared notes (will expire April 2024) - IVOA_26Feb_PTTT.pdf
  3. Mon 25 Mar 2024 20:00 UTC - yopad shared notes (will expire May 2024) - IVOA_26Mar_PTTT.pdf
  4. Mon 22 Apr 2024 20:00 UTC - yopad shared notes (will expire June 2024) - IVOA_26Apr_PTTT.pdf
Changed:
<
<
  1. Thu/Fri May 16/17 Sydney 10am Local time; Agenda - PTTT_May1617_Schedule.pdf
>
>
  1. Thu/Fri May 16/17 Sydney 10am Local time; Agenda - PTTT_May1617_Schedule.pdf - yopad shared notes
 

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

META FILEATTACHMENT attachment="IVOA_22Jan_PTTT.pdf" attr="" comment="" date="1707955225" name="IVOA_22Jan_PTTT.pdf" path="IVOA_22Jan_PTTT.pdf" size="40242" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Feb_PTTT.pdf" attr="" comment="" date="1709843589" name="IVOA_26Feb_PTTT.pdf" path="IVOA_26Feb_PTTT.pdf" size="51556" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Mar_PTTT.pdf" attr="" comment="" date="1712057496" name="IVOA_26Mar_PTTT.pdf" path="IVOA_26Mar_PTTT.pdf" size="49847" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Apr_PTTT.pdf" attr="" comment="" date="1715070579" name="IVOA_26Apr_PTTT.pdf" path="IVOA_26Apr_PTTT.pdf" size="41597" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="PTTT_May1617_Schedule.pdf" attr="" comment="PTTT Face to Face schedule - May 16/17" date="1715809026" name="PTTT_May1617_Schedule.pdf" path="PTTT_May1617_Schedule.pdf" size="55725" user="JanetEvans" version="1"

Revision 262024-05-15 - JanetEvans

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

  1. 22 Jan 2024 at 20:00 UTC - yopad shared notes - IVOA_22Jan_PTTT.pdf
  2. 26 Feb 2024 at 20:00 UTC - yopad shared notes (will expire April 2024) - IVOA_26Feb_PTTT.pdf
  3. Mon 25 Mar 2024 20:00 UTC - yopad shared notes (will expire May 2024) - IVOA_26Mar_PTTT.pdf
Changed:
<
<
  1. Mon 22 Apr 2024 20:00 UTC - yopad shared notes (will expire June 2024) - IVOA_26Apr_PTTT.pdf
>
>
  1. Mon 22 Apr 2024 20:00 UTC - yopad shared notes (will expire June 2024) - IVOA_26Apr_PTTT.pdf
Added:
>
>
  1. Thu/Fri May 16/17 Sydney 10am Local time; Agenda - PTTT_May1617_Schedule.pdf
 

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->
Added:
>
>
 
META FILEATTACHMENT attachment="IVOA_22Jan_PTTT.pdf" attr="" comment="" date="1707955225" name="IVOA_22Jan_PTTT.pdf" path="IVOA_22Jan_PTTT.pdf" size="40242" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Feb_PTTT.pdf" attr="" comment="" date="1709843589" name="IVOA_26Feb_PTTT.pdf" path="IVOA_26Feb_PTTT.pdf" size="51556" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Mar_PTTT.pdf" attr="" comment="" date="1712057496" name="IVOA_26Mar_PTTT.pdf" path="IVOA_26Mar_PTTT.pdf" size="49847" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Apr_PTTT.pdf" attr="" comment="" date="1715070579" name="IVOA_26Apr_PTTT.pdf" path="IVOA_26Apr_PTTT.pdf" size="41597" user="JamesDempsey" version="1"
Added:
>
>
META FILEATTACHMENT attachment="PTTT_May1617_Schedule.pdf" attr="" comment="PTTT Face to Face schedule - May 16/17" date="1715809026" name="PTTT_May1617_Schedule.pdf" path="PTTT_May1617_Schedule.pdf" size="55725" user="JanetEvans" version="1"
 

Revision 252024-05-07 - JamesDempsey

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

  1. 22 Jan 2024 at 20:00 UTC - yopad shared notes - IVOA_22Jan_PTTT.pdf
  2. 26 Feb 2024 at 20:00 UTC - yopad shared notes (will expire April 2024) - IVOA_26Feb_PTTT.pdf
  3. Mon 25 Mar 2024 20:00 UTC - yopad shared notes (will expire May 2024) - IVOA_26Mar_PTTT.pdf
Changed:
<
<
  1. Mon 22 Apr 2024 20:00 UTC - yopad shared notes
>
>
  1. Mon 22 Apr 2024 20:00 UTC - yopad shared notes (will expire June 2024) - IVOA_26Apr_PTTT.pdf
 

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

META FILEATTACHMENT attachment="IVOA_22Jan_PTTT.pdf" attr="" comment="" date="1707955225" name="IVOA_22Jan_PTTT.pdf" path="IVOA_22Jan_PTTT.pdf" size="40242" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Feb_PTTT.pdf" attr="" comment="" date="1709843589" name="IVOA_26Feb_PTTT.pdf" path="IVOA_26Feb_PTTT.pdf" size="51556" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Mar_PTTT.pdf" attr="" comment="" date="1712057496" name="IVOA_26Mar_PTTT.pdf" path="IVOA_26Mar_PTTT.pdf" size="49847" user="JamesDempsey" version="1"
Added:
>
>
META FILEATTACHMENT attachment="IVOA_26Apr_PTTT.pdf" attr="" comment="" date="1715070579" name="IVOA_26Apr_PTTT.pdf" path="IVOA_26Apr_PTTT.pdf" size="41597" user="JamesDempsey" version="1"
 

Revision 242024-04-17 - JamesDempsey

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

  1. 22 Jan 2024 at 20:00 UTC - yopad shared notes - IVOA_22Jan_PTTT.pdf
  2. 26 Feb 2024 at 20:00 UTC - yopad shared notes (will expire April 2024) - IVOA_26Feb_PTTT.pdf
  3. Mon 25 Mar 2024 20:00 UTC - yopad shared notes (will expire May 2024) - IVOA_26Mar_PTTT.pdf
Added:
>
>
  1. Mon 22 Apr 2024 20:00 UTC - yopad shared notes
 

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

META FILEATTACHMENT attachment="IVOA_22Jan_PTTT.pdf" attr="" comment="" date="1707955225" name="IVOA_22Jan_PTTT.pdf" path="IVOA_22Jan_PTTT.pdf" size="40242" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Feb_PTTT.pdf" attr="" comment="" date="1709843589" name="IVOA_26Feb_PTTT.pdf" path="IVOA_26Feb_PTTT.pdf" size="51556" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Mar_PTTT.pdf" attr="" comment="" date="1712057496" name="IVOA_26Mar_PTTT.pdf" path="IVOA_26Mar_PTTT.pdf" size="49847" user="JamesDempsey" version="1"

Revision 232024-04-02 - JamesDempsey

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

  1. 22 Jan 2024 at 20:00 UTC - yopad shared notes - IVOA_22Jan_PTTT.pdf
  2. 26 Feb 2024 at 20:00 UTC - yopad shared notes (will expire April 2024) - IVOA_26Feb_PTTT.pdf
Changed:
<
<
  1. Mon 25 Mar 2024 20:00 UTC - yopad shared notes (will expire May 2024) -
>
>
  1. Mon 25 Mar 2024 20:00 UTC - yopad shared notes (will expire May 2024) - IVOA_26Mar_PTTT.pdf
 

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

META FILEATTACHMENT attachment="IVOA_22Jan_PTTT.pdf" attr="" comment="" date="1707955225" name="IVOA_22Jan_PTTT.pdf" path="IVOA_22Jan_PTTT.pdf" size="40242" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Feb_PTTT.pdf" attr="" comment="" date="1709843589" name="IVOA_26Feb_PTTT.pdf" path="IVOA_26Feb_PTTT.pdf" size="51556" user="JamesDempsey" version="1"
Added:
>
>
META FILEATTACHMENT attachment="IVOA_26Mar_PTTT.pdf" attr="" comment="" date="1712057496" name="IVOA_26Mar_PTTT.pdf" path="IVOA_26Mar_PTTT.pdf" size="49847" user="JamesDempsey" version="1"
 

Revision 222024-03-25 - JamesDempsey

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

  1. 22 Jan 2024 at 20:00 UTC - yopad shared notes - IVOA_22Jan_PTTT.pdf
  2. 26 Feb 2024 at 20:00 UTC - yopad shared notes (will expire April 2024) - IVOA_26Feb_PTTT.pdf
Changed:
<
<
  1. Mon 25 Mar 2024 20:00 UTC
>
>
  1. Mon 25 Mar 2024 20:00 UTC - yopad shared notes (will expire May 2024) -
 

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

META FILEATTACHMENT attachment="IVOA_22Jan_PTTT.pdf" attr="" comment="" date="1707955225" name="IVOA_22Jan_PTTT.pdf" path="IVOA_22Jan_PTTT.pdf" size="40242" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Feb_PTTT.pdf" attr="" comment="" date="1709843589" name="IVOA_26Feb_PTTT.pdf" path="IVOA_26Feb_PTTT.pdf" size="51556" user="JamesDempsey" version="1"

Revision 212024-03-21 - JamesDempsey

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

  1. 22 Jan 2024 at 20:00 UTC - yopad shared notes - IVOA_22Jan_PTTT.pdf
Changed:
<
<
  1. 26 Feb 2024 at 20:00 UTC - yopad shared notes (will expire April 2024) - IVOA_22Jan_PTTT.pdf
>
>
  1. 26 Feb 2024 at 20:00 UTC - yopad shared notes (will expire April 2024) - IVOA_26Feb_PTTT.pdf
 
  1. Mon 25 Mar 2024 20:00 UTC

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

META FILEATTACHMENT attachment="IVOA_22Jan_PTTT.pdf" attr="" comment="" date="1707955225" name="IVOA_22Jan_PTTT.pdf" path="IVOA_22Jan_PTTT.pdf" size="40242" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Feb_PTTT.pdf" attr="" comment="" date="1709843589" name="IVOA_26Feb_PTTT.pdf" path="IVOA_26Feb_PTTT.pdf" size="51556" user="JamesDempsey" version="1"

Revision 202024-03-12 - GregoryDuboisFelsmann

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Changed:
<
<
>
>
 

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

  1. 22 Jan 2024 at 20:00 UTC - yopad shared notes - IVOA_22Jan_PTTT.pdf
  2. 26 Feb 2024 at 20:00 UTC - yopad shared notes (will expire April 2024) - IVOA_22Jan_PTTT.pdf
  3. Mon 25 Mar 2024 20:00 UTC

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

META FILEATTACHMENT attachment="IVOA_22Jan_PTTT.pdf" attr="" comment="" date="1707955225" name="IVOA_22Jan_PTTT.pdf" path="IVOA_22Jan_PTTT.pdf" size="40242" user="JamesDempsey" version="1"
META FILEATTACHMENT attachment="IVOA_26Feb_PTTT.pdf" attr="" comment="" date="1709843589" name="IVOA_26Feb_PTTT.pdf" path="IVOA_26Feb_PTTT.pdf" size="51556" user="JamesDempsey" version="1"

Revision 192024-03-07 - JamesDempsey

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

Changed:
<
<
  1. 22 Jan - yopad shared notes - IVOA_22Jan_PTTT.pdf
  2. 26 Feb 2024 at 20:00 UTC - yopad shared notes (will expire April 2024) - PDF TBA
>
>
  1. 22 Jan 2024 at 20:00 UTC - yopad shared notes - IVOA_22Jan_PTTT.pdf
  2. 26 Feb 2024 at 20:00 UTC - yopad shared notes (will expire April 2024) - IVOA_22Jan_PTTT.pdf
Added:
>
>
  1. Mon 25 Mar 2024 20:00 UTC
 

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

META FILEATTACHMENT attachment="IVOA_22Jan_PTTT.pdf" attr="" comment="" date="1707955225" name="IVOA_22Jan_PTTT.pdf" path="IVOA_22Jan_PTTT.pdf" size="40242" user="JamesDempsey" version="1"
Added:
>
>
META FILEATTACHMENT attachment="IVOA_26Feb_PTTT.pdf" attr="" comment="" date="1709843589" name="IVOA_26Feb_PTTT.pdf" path="IVOA_26Feb_PTTT.pdf" size="51556" user="JamesDempsey" version="1"
 

Revision 182024-02-15 - JamesDempsey

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

Changed:
<
<
  1. 22 Jan - yopad shared notes - PDF TBA
>
>
  1. 22 Jan - yopad shared notes - IVOA_22Jan_PTTT.pdf
Added:
>
>
  1. 26 Feb 2024 at 20:00 UTC - yopad shared notes (will expire April 2024) - PDF TBA
 

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->
Added:
>
>
META FILEATTACHMENT attachment="IVOA_22Jan_PTTT.pdf" attr="" comment="" date="1707955225" name="IVOA_22Jan_PTTT.pdf" path="IVOA_22Jan_PTTT.pdf" size="40242" user="JamesDempsey" version="1"

Revision 172024-02-14 - JanetEvans

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Added:
>
>
 

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

  1. 22 Jan - yopad shared notes - PDF TBA

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

Revision 162024-01-23 - BrianMajor

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Added:
>
>
 

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

Changed:
<
<
  1. 22 Jan - yopad shared notes - PDF TBA
>
>
  1. 22 Jan - yopad shared notes - PDF TBA
 

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

Revision 152024-01-22 - DaveMorris

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

Changed:
<
<
The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.
>
>
The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.
 

Membership - email alias "P3T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Meetings

  1. 22 Jan - yopad shared notes - PDF TBA

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

Revision 142024-01-22 - JamesDempsey

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

Added:
>
>

Meetings

  1. 22 Jan - yopad shared notes - PDF TBA
 

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

Revision 132024-01-18 - AdrianDamian

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Added:
>
>
 

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

Revision 122024-01-09 - PaulHarrison

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Changed:
<
<
>
>
 

Related GitHub issues (add yours)

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->
Deleted:
<
<

Revision 112024-01-05 - TomDonaldson

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
  • May Interop : May 20-24; TCG mtg: May 19

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Added:
>
>
 
Deleted:
<
<
 

Related GitHub issues (add yours)

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->
Added:
>
>

Revision 102024-01-02 - JanetEvans

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
Changed:
<
<
  • Plan to meet in Sydney 2 days (perhaps Thu/Fri) prior to IVOA that starts on Sunday (discussed with Simon/is doable)
>
>
  • Plan to meet in Sydney 2 days (Thu/Fri, May 16/17) prior to IVOA that starts on Sunday (discussed with Simon/he can do it)
Added:
>
>
  • May Interop : May 20-24; TCG mtg: May 19
 

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Related GitHub issues (add yours)

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

Revision 92024-01-02 - JanetEvans

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Added:
>
>
 

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (perhaps Thu/Fri) prior to IVOA that starts on Sunday (discussed with Simon/is doable)

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Changed:
<
<
*
>
>
 

Related GitHub issues (add yours)

Deleted:
<
<
 

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->
Deleted:
<
<

Revision 82023-12-15 - DaveMorris

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (perhaps Thu/Fri) prior to IVOA that starts on Sunday (discussed with Simon/is doable)

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

Changed:
<
<
>
>
*
Added:
>
>

Related GitHub issues (add yours)

 

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

Revision 72023-12-15 - JanetEvans

 
META TOPICPARENT name="IvoaTCG"

Protocol Transitioning Tiger Team (P3T)

The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "P3T"

Changed:
<
<
>
>
 

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
Changed:
<
<
  • Plan to meet in Sydney 2 days (perhaps Thu/Fri) prior to IVOA that starts on Sunday (needs discussion and inquiry woth Organizers/Exec)
>
>
  • Plan to meet in Sydney 2 days (perhaps Thu/Fri) prior to IVOA that starts on Sunday (discussed with Simon/is doable)
 

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->
Added:
>
>

Revision 62023-12-12 - JanetEvans

 
META TOPICPARENT name="IvoaTCG"
Changed:
<
<

Protocol Transitioning Tiger Team (P3T)

>
>

Protocol Transitioning Tiger Team (P3T)

  The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Changed:
<
<

Membership - email alias "PM2T"

>
>

Membership - email alias "P3T"

 

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (perhaps Thu/Fri) prior to IVOA that starts on Sunday (needs discussion and inquiry woth Organizers/Exec)

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

Revision 52023-12-12 - JanetEvans

 
META TOPICPARENT name="IvoaTCG"
Changed:
<
<

Protocol Modernization Tiger Team (PM2T)

>
>

Protocol Transitioning Tiger Team (P3T)

 
Changed:
<
<
The Protocol Modernization Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.
>
>
The Protocol Transitioning Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.
  The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "PM2T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (perhaps Thu/Fri) prior to IVOA that starts on Sunday (needs discussion and inquiry woth Organizers/Exec)

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

Revision 42023-12-11 - MarcoMolinaro

 
META TOPICPARENT name="IvoaTCG"

Protocol Modernization Tiger Team (PM2T)

The Protocol Modernization Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "PM2T"

Changed:
<
<
  • Gilles Landais - kgillies@tmt.org (If we are volunteering to help with creating service APIs in OPENAPI, I would participate)
>
>
  • Kim Gillies - kgillies@tmt.org (If we are volunteering to help with creating service APIs in OPENAPI, I would participate)
 

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (perhaps Thu/Fri) prior to IVOA that starts on Sunday (needs discussion and inquiry woth Organizers/Exec)

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<--  
-->

Revision 32023-12-11 - MarcoMolinaro

 
META TOPICPARENT name="IvoaTCG"

Protocol Modernization Tiger Team (PM2T)

The Protocol Modernization Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "PM2T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (perhaps Thu/Fri) prior to IVOA that starts on Sunday (needs discussion and inquiry woth Organizers/Exec)

Standards Involved (1st up!)

  • CS
  • UWS
  • TAP
  • VOSpace

OpenAPI Project Links (add yours)

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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
Changed:
<
<
<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->
>
>

Revision 22023-12-11 - DaveMorris

 
META TOPICPARENT name="IvoaTCG"

Protocol Modernization Tiger Team (PM2T)

The Protocol Modernization Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "PM2T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (perhaps Thu/Fri) prior to IVOA that starts on Sunday (needs discussion and inquiry woth Organizers/Exec)

Standards Involved (1st up!)

Added:
>
>
  • CS
 
  • UWS
Deleted:
<
<
  • VOSpace
 
  • TAP
Added:
>
>
  • VOSpace
 

OpenAPI Project Links (add yours)

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->

Deleted:
<
<

Revision 12023-12-08 - JanetEvans

 
META TOPICPARENT name="IvoaTCG"

Protocol Modernization Tiger Team (PM2T)

The Protocol Modernization Tiger Team was formed in Tucson at the Interop meeting in Nov 2023. The aim is to address the question of compatibility of the DAL protocols (and by implication protocols such as UWS) with modern web development tools. A number of people volunteered to form a tiger team to work on this.

The recommendations being examined would mostly be in DAL and GWS (e.g., TAP, SIA2, SODA, UWS) so will need to be a cross WG effort. A question to answer is : How do we adapt the protocol interactions to be compatible with tools such as OpenAPI.

Membership - email alias "PM2T"

Initial Plan forward

  • Setup a wiki & mail list
  • Meet over 4 months ... Jan - April (once a month)
  • Plan to meet in Sydney 2 days (perhaps Thu/Fri) prior to IVOA that starts on Sunday (needs discussion and inquiry woth Organizers/Exec)

Standards Involved (1st up!)

  • UWS
  • VOSpace
  • TAP

OpenAPI Project Links (add yours)

References

From Tucson DAL session YoPAD

  • 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
    JD: Is OpenAPI a useful step?
    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

<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->

 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback