See also: IRC log
<trackbot> Date: 30 June 2015
wrong teleconference!
we are using webex now: Approve Minutes of previous meeting
oops, bad paste
june 9: http://wiki.hl7.org/index.php?title=ITS_RDF_Concall_Minutes_20150609
june 16: http://wiki.hl7.org/index.php?title=ITS_RDF_Concall_Minutes_20150616
june 23: http://wiki.hl7.org/index.php?title=ITS_RDF_Concall_Minutes_20150623
APPROVED: Minutes june 9, 16 and 23
david: Update: Still being discussed in ArB, once it passes there an updated version will be distributed
Three options: https://goo.gl/DKcm0U
david: on Wednesday TF call, we
agreed on option 1
... uses a fhir:index property
paul: Same approach as in other work we've done
lloyd: motion to go with option 1
david: seconded
AGREED: use option 1
1. FHIR RDF: HTML page (already started) explaining FHIR RDF serialization (equivalent to existing FHIR XML and JSON pages)
2. FHIR ontology explanation page, explaining how FHIR structure definitions and other conformance resource can be expressed using OWL
3. Modify the supported reference implementations to consume/produce RDF, just as for XML and JSON.
4. Modify the FHIR spec build process, so when it produces JSON versions of everything and tests roundtripping, it also produces RDF versions of everything and tests roundtripping for RDF.
5. Downloadable FHIR ontology (generated by the FHIR spec build process?)
6. ShEx implementation of FHIR XML<->RDF round tripping, for use as a reference implementation for the RDF reference implementations
marc: Lloyd worked on 1, and Eric on #6.
lloyd: Grahame worked on #1.
david: For #2?
lloyd: I can integrate it into the build process, but reluctant to be a primary author.
tony: Volunteering as editor on #2.
david: we should start getting a draft of a page for #2 online
<Marc_Twagirumukiza> #1 and #2 seems to be related
lloyd: need xhtml content
... send email saying you agree to chapter 16, and i'll give
you write access
<Marc_Twagirumukiza> and I think Lloyd is in best position as editor
lloyd: #4 will likely be Grahame
david: address that after the ShEx implementation ready
rafael: Any discussion of JSON-LD?
david: explored that possibility,
but JSON-LD does not handle context sensitivity, so we could
not use it.
... #5? Tony?
tony: no, because that is
generated by the build process. would shex generate it?
... we could start from hand-generated ont.
... Maybe #5 would come out of shex also.
david: #6 would be eric I think
http://wiki.hl7.org/index.php?title=File:FHIR_RDF_Sample_side_by_side_comparisons.pdf
http://wiki.hl7.org/images/2/25/FHIR_RDF_Sample_side_by_side_comparisons.pdf
lloyd: Expose 'status' as a pseudo-CodeableConcept
tony: local codes move to
CodeableConcept
... range of status should be the valueset
lloyd: ont constraints would be
on code datatype -- that it's a codeable thingy with only one
coding.
... And in the structure def that does the binding, the binding
would assert that at least one of the codings for status must
be an instance of the class of the valueset
... and the valueset would insist that it is allergy
status.
<scribe> ACTION: Tony to update line 395 to use CodeableThingy [recorded in http://www.w3.org/2015/06/30-hcls-minutes.html#action01]
<trackbot> Error finding 'Tony'. You can review and register nicknames at <http://www.w3.org/2014/HCLS/track/users>.
line 402-434
tony: using classes for the
valuesets, and classes for the concepts in those
valuesets
... lines 415-422
lines 406-411
lloyd: every property will have a
cardinality assertion.
... A second assertion will say if you have a fhir code, there
is one coding
... valueset assertion would have to be on the coding part --
not the valueset itself
david: What needs to be changed to section 3.2.3?
tony: need to incorporate CodeableThingy
lloyd: Would be easier to
separate the cardinality assertions to where they go. Bindings
should be visually distinct from the cardinality
assertions.
... Some cardinalities will show up in datatypes though.
... cardinality restriction can be separated.
<scribe> ACTION: Tony to separate the cardinality from the binding to the valuesets [recorded in http://www.w3.org/2015/06/30-hcls-minutes.html#action02]
<trackbot> Error finding 'Tony'. You can review and register nicknames at <http://www.w3.org/2014/HCLS/track/users>.
lloyd: valueset itself should be
instance based -- not class based.
... system is always a specific URL.
... valueset says this valueset has system X
david: What lines would change?
lloyd: 418-22 would go away, and
be replaced by a constraint on the system property of the
coding.
... expressed as a value constraint on the datatypeProperty of
codingThingy.system
... Valuesets are value constraints on Coding.
... They can be an enumeration, or regex on the codes, or a
wide variety of things.
tony: instances of valuesets are
concepts.
... valueset space is a class that expresses a filter on the
allowed codings.
<scribe> ACTION: Tony to work out changes to section 3.2.3 [recorded in http://www.w3.org/2015/06/30-hcls-minutes.html#action03]
<trackbot> Error finding 'Tony'. You can review and register nicknames at <http://www.w3.org/2014/HCLS/track/users>.
ADJOURNED
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: dbooth Inferring Scribes: dbooth Default Present: +1.510.418.aaaa Present: Sajjad Claude David_Booth Marc_T Brian_Pech Lloyd_McKenzie Paul_Courtney Paul_Knapp Rafael_Richards Rob_Hausam Tony_Mallia Found Date: 30 Jun 2015 Guessing minutes URL: http://www.w3.org/2015/06/30-hcls-minutes.html People with action items: tony[End of scribe.perl diagnostic output]