15:05:57 RRSAgent has joined #hcls 15:05:57 logging to http://www.w3.org/2015/06/17-hcls-irc 15:05:59 RRSAgent, make logs world 15:06:01 Zakim has joined #hcls 15:06:01 Zakim, this will be HCLS 15:06:02 Meeting: Semantic Web Health Care and Life Sciences Interest Group Teleconference 15:06:02 Date: 17 June 2015 15:06:02 ok, trackbot, I see SW_HCLS()11:00AM already started 15:06:16 Topic: Agenda 15:06:26 Eric: transformation softward 15:06:34 Tony: References, in side-by-side 15:06:47 dbooth: ordered lists 15:07:05 Topic: Transformation Software 15:07:11 s/softward/software/ 15:07:27 Eric: You give this an input XML doc, and it spits out the RDF 15:07:42 - +1.310.266.aaaa 15:07:43 SW_HCLS()11:00AM has ended 15:07:43 Attendees were +1.310.266.aaaa 15:07:43 -> http://www.w3.org/2015/06/FHIR-RDF/fromXML FHIR/XML to RDF (Turtle) 15:07:49 Lloyd has joined #HCLS 15:08:13 -> http://www.w3.org/2015/06/FHIR-RDF/fromXML FHIR/XML to RDF (Turtle) 15:10:02 Don has joined #HCLS 15:10:06 -> http://www.w3.org/2015/06/FHIR-RDF/fromXML FHIR/XML to RDF (Turtle) 15:12:32 Tony has joined #HCLS 15:14:34 eric: Put in a URL for some FHIR XML, and it gives you back FHIR RDF, in Turtle. 15:15:16 ... The ShEx for this is generated from the FHIR schema definitions. 15:15:52 ... Plus there's some special handling code. 15:16:20 ... I'm also working on getting it to handle the profiles used for defining, e.g., specializations to quantity. 15:17:08 q+ 15:18:37 -> https://www.w3.org/wiki/HCLS/ClinicalObservationsInteroperability/FHIR#parameters parameters 15:21:56 dbooth: eric, please add a link to explanation of the parameters of that form 15:22:48 dbooth: suggest that we adopt eric's ShEx transformation as our first reference implementation for transforming FHIR XML to FHIR RDF 15:23:16 ... FHIR XML and JSON use spec descriptions and reference implementations. 15:23:32 ... Suggest we do the same for FHIR RDF. 15:23:47 tony: What about the ontology? 15:23:59 lloyd: That's separate. 15:25:02 ... We're really defining the base conversion algorithm, for converstion from FHIR structure def and value set and possibly concept map resource instances to OWL and/or RDFS expression that means the same thing, in terms of defining the classes. 15:25:56 HCLS has joined #HCLS 15:26:42 HCLS has left #hcls 15:27:53 dbooth: 1. HTML page that describes (mostly in prose) the FHIR RDF (instance data). 15:28:21 dbooth: 2. Multiple reference implementations for generating FHIR RDF instance data (from FHIR XML, for example). 15:28:36 lloyd: Rather phrase that as adjusting existing implemntations to handle RDF also. 15:29:01 dbooth: 3. FHIR RDF Ontology. This will be generated (partially) from the FHIR schemas. 15:29:17 s/schemas/conformance resources 15:30:19 tony: is there a formal def of the transformation? 15:30:57 lloyd: no. we describe how to express instances from the structure model in particular serializations. 15:33:35 ... 4. A page describing the OWL representation of FHIR artifacts. Describes #3. What is RDF/OWL, where might they be useful? HOw do core concepts in structure defs correspond to RDF constructs? How to integrate FHIR ontology w other ontologies? e.g., using SNOMED ont. 15:34:54 ... Whole point of FHIR is to make it easy for implementers to do things. There will be people who come to FHIR who may want to know how to use FHIR RDF, and we need to give them that guidance. 15:35:53 eric: How does the ShEx transformation fit in? 15:36:31 q+ to suggest that the ShEx implementation be used as a ref impl for the RDF ref impls :) 15:38:41 lloyd: conformance resources: conformance, structure, value systems, concept maps (def links between terminologies or structures), data elements, operation defs, naming system (here's how different URIs map to each other -- not sure how to expose in OWL -- maps one namespace to another), test scripts. 15:41:08 ack dbooth 15:41:08 dbooth, you wanted to suggest that the ShEx implementation be used as a ref impl for the RDF ref impls :) 15:42:37 dbooth: The ShEx script could be viewed as a formal def of our desired XML-RDF translation 15:42:45 lloyd: It 15:43:19 lloyd: It's a tech. I expect at least some of the ref imple to be modified to produce/consume RDF. The doc should be agnostic. 15:44:34 lloyd: Every ref impl will able to produce/consume RDF. 15:45:36 ... Ref impl should be able to consume Turtle, RDF/XML and various RDF syntaxes. Libraries can convert between RDF implementations. 15:45:55 ... That's on the instance data side. 15:46:40 ... For class def side, that's not so clearly in the ref impl side, we should discuss whether the ref impl should produce/consume. 15:46:54 dbooth: What should they produce/consume for ontology? 15:47:27 lloyd: If an XML schema were provided, it could spit out an ontology for it. 15:48:09 ... The pub process produces the ref impl, and they are used to produce the JSON versions. It also does a round trip check. 15:48:40 ... Both for example instance data and for profiles. 15:48:51 ... The pub process reads spreadsheets and produces profile XML files. 15:49:29 ... The ref impl takes those and turns them into profile JSON files. Once we have RDF going, it will produce profile RDF files also. 15:50:14 dbooth: Seems like we need to better understand the pub process to know what parts to add in for RDF. 15:51:48 lloyd: Need to create the two HTML pages (equiv to existing XML and JSON syntax pages; and FHIR as ontology page, that talks about how FHIR structure defs and other conformance resource can be expressed using OWL) 15:52:28 ... Need to have modified the supported ref impls to consume/produce RDF, just as for XML and JSON. 15:53:27 ... Need to modify the build process, so when it produces JSON versions of everything and tests roundtripping, it also produces RDF versions of everything and tests roundtripping for that. 15:55:22 dbooth: suggest that the ShEx implementation be used as a ref impl for the RDF ref impls 15:55:31 ... others agree? 15:55:48 tony: valuable to have it as an independent testing mechanism. 15:56:13 eric: allows people to validate in a generic tool without having to roll out a ref impl. 15:56:26 ... Much use of the XML schema in the wild? 15:56:47 lloyd: yes. we use it internally to guide examples, and for validating. 15:57:21 ... Some implementers use it and run into all of the issues associated with that. 16:00:39 AGREED: Use ShEx implementation as a reference implementation for the RDF reference implementations 16:00:53 eric: Could use some others hacking on the ShEx 16:01:10 dbooth: i am planning to do so, but have been trying to finish another project first. 16:05:19 dbooth: What needs to be done to move the ShEX to github for others to collaboration? 16:05:38 eric: Mostly people give me their github IDs, so that I can add them. 16:08:37 eric: today showed the XML-RDF direction. Still working on the ShEx part for the other direction: RDF->XML. 16:08:53 Chair: David Booth 16:14:26 Present: Tony Mallia, David Booth, Lloyd McKenzie, EricP, Don Doherty 16:14:32 rrsagent, draft minutes 16:14:32 I have made the request to generate http://www.w3.org/2015/06/17-hcls-minutes.html dbooth 16:36:20 egonw__ has joined #HCLS 17:10:04 egonw__ has joined #HCLS 17:15:04 egonw has joined #HCLS 17:17:03 egonw_ has joined #HCLS 17:27:41 egonw_ has joined #HCLS 17:37:20 egonw_ has joined #HCLS 17:40:45 egonw__ has joined #HCLS 17:41:14 egonw has joined #HCLS 17:54:15 Zakim has left #hcls