1 / 11

ADTF Informational Session

ADTF Informational Session. Common Terminology Services 2 (CTS2) XML to JSON Transformation Rules Request For Comment September 16 th , 2013 Cory Endle, Craig Stancl Mayo Clinic. Meeting Goals. Background/History Review CTS2 JSON RFC Rules XML to JSON Implementations Proposed Process

kirk-snider
Download Presentation

ADTF Informational Session

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ADTF Informational Session Common Terminology Services 2 (CTS2)XML to JSON Transformation Rules Request For Comment September 16th, 2013Cory Endle, Craig Stancl Mayo Clinic

  2. Meeting Goals • Background/History • Review CTS2 JSON RFC Rules • XML to JSON Implementations • Proposed Process • JSON RFC Anticipated Timeline • Questions

  3. CTS2 JSON Background/History • CTS2 representation (at a PSM) level is XML. • With XSDs, we can specify exact structure, and have a mechanism for validating correctness. • XSDs are expressive enough to allow for the model constraints.

  4. CTS2 JSON Background/History Clients demand JSON. Implementers will most likely expose some sort of JSON representation of CTS2. • Currently, no standard representation of CTS2 in JSON. • JSON may not be interoperable, as slight differences in JSON renderings are common among different libraries. There is no JSON validation.

  5. CTS2 JSON Background/History • At the June 2013 Berlin OMG meeting, we discussed this issue with Andrew Watson and Tom Rutt. • We decided to make CTS2 specific rules for transforming XML to JSON. These rules will be captured in this RFC. • Implementers can then follow these rules to modify or create JSON libraries or transformation tools.

  6. Review CTS2 JSON RFC • Review JSON RFC document: • Common Terminology Services 2 (CTS2) XML to JSON Transformation Rules Request For Comment

  7. XML to JSON Implementations • Implementation • XSLT to transform XML to JSON • Application/Services utilizing the XSLT: • Internal CTS2 service • py4cts2 • UI to test XML to JSON rules • http://informatics.mayo.edu/cts2/services/xmlToJson/

  8. Proposed ProcessParallel or Linear? • JSON RFC and CTS2 RTF 1.2 running in parallel. • Expect the JSON RFC FTF to be complete in time to be included into the CTS2 RTF 1.2. • There will be a final report for both the RFC FTF and CTS2 RTF 1.2. • Include a combined convenience document with changes from both RFC FTF and CTS2 RTF 1.2.

  9. Anticipated JSON RFC Timeline • August 24 - JSON RFC - LOI submitted • Sept 2013 - JSON RFC - ADTF and AB Endorsement of RFC • Sept 2013 - JSON RFC - PTC issue RFC 90 day review • Dec 2013 - JSON RFC - RFC 90 day review Complete • Dec 2013 - JSON RFC - ADTF, AB, PTC approvals and issuance of "Beta" specification • Dec 2013 - JSON RFC - Issue FTF process for JSON RFC • February 2014 - JSON RFC - Submit FTF report 4 weeks prior to OMG March 2014 meeting

  10. Anticipated JSON RFC Timeline (Continued) • March 2014 – JSON RFC - FTF report due (4 week rule) • March 2014 - JSON RFC – FTF report approval by AB and PTC • June 2014 - JSON RFC - RFC BoD adoption Vote - FINAL JSON SPEC • June 2014 - JSON RFC - Specification Management Subcommittee (SMSC) --- Obtain recommendation on how to include JSON RFC into CTS2 • June 2014 - August 2014 - Consider JSON RFC for RTF 1.2 • August 18, 2014 - RTF 1.2 – RTF 1.2 Report due (4 week rule)

  11. Questions

More Related