This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "ITS RDF ConCall Agenda"

From HL7Wiki
Jump to navigation Jump to search
Line 12: Line 12:
 
See also [http://wiki.hl7.org/index.php?title=RDF_for_Semantic_Interoperability#Work_Projects Work Projects]
 
See also [http://wiki.hl7.org/index.php?title=RDF_for_Semantic_Interoperability#Work_Projects Work Projects]
  
==  Agenda for 12-May-2015 (Paris) ==
+
==  Agenda for 12-May-2015 ==
 
# Role call and agenda
 
# Role call and agenda
 
# Moderation and use of a SPEAKER QUEUE
 
# Moderation and use of a SPEAKER QUEUE

Revision as of 18:11, 11 May 2015

Return to ITS Main Page | ITS RDF Minutes 2015 | All ITS RDF Pages | ITS Email Archives | W3C HCLS Email Archives | Issues List | W3C Clinical Observations Interoperability

Weekly joint teleconference of the HL7 ITS subgroup on RDF for Semantic Interoperability and the W3C Healthcare and Life Sciences group on Clinical Observations Interoperability.

See also Work Projects

Agenda for 12-May-2015

  1. Role call and agenda
  2. Moderation and use of a SPEAKER QUEUE
  3. Pick a scribe
  4. Approve Minutes of previous meetings
    1. May 5
    2. May 11 Paris
  5. Review of Action Items
    1. ACTION: JohnMattison to provide example CCDA for trying with ShEx [recorded in http://www.w3.org/2014/12/23-hcls-minutes.html#action02]
  6. FHIR RDF and Validation/Translation Task Force (Wednesdays 11am Boston timezone, same teleconference details as below except for the day)
    1. Moderation and use of a SPEAKER QUEUE
    2. Notes from the most recent task force teleconference
    3. blank nodes as CodeableConcept instances
    4. Side-by-side example of two FHIR RDF approaches - references (Tony Mallia)
      http://wiki.hl7.org/images/1/19/FHIR_RDF_Sample_side_by_side_comparisons_v2.pdf
      1. ISSUE-8 - If we treat observation.code as an instance of a class, should that class represent the disease itself or a *description* of the disease?
        1. Kerstin suggests: https://code.google.com/p/ogms/
      2. ISSUE-9 - Does observation.code need to be a uri instead of a blank node, to work well with owl reasoners?
    5. FHIR element ordering. Some possibilities:
      1. rdf:List
      2. Ordered List Ontology
      3. Collections Ontology
      4. Simple List Conventions
  7. Planning Upcoming HL7 Meeting - Paris May 10-15
    1. http://www.hl7.org/events/wgm052015/
    2. Chair: Rob Hausam (acting chair for ITS) with Claude Nanjo
    3. Will attend: Claude, Paul, Rob, EricP, Andy Stechin
    4. Will not attend: David, Marc, Tony
    5. ITS meeting slot for RDF group: Monday Q4 (3:30pm Paris time)
  8. Side-by-side example of two FHIR RDF approaches (Tony Mallia)
    http://wiki.hl7.org/images/1/19/FHIR_RDF_Sample_side_by_side_comparisons_v2.pdf
    OLD: http://wiki.hl7.org/images/2/25/FHIR_RDF_Sample_side_by_side_comparisons.pdf
  9. Continuing on FHIR RDF:
    1. FHIR element ordering. Some possibilities:
      1. rdf:List
      2. Ordered List Ontology
      3. Collections Ontology
      4. Simple List Conventions
    2. What URI to use for observation.code instance, or whether to use a blank node, which does not work well with owl reasoners. Potential Options: 1. use blank nodes and let applications deal with the problem by minting skolem URIs or something else; 2. define a standard way to form a URI; 3. use a skolem URI using the well-known convention defined by RDF. http://www.w3.org/TR/rdf11-concepts/#h3_section-skolemization

Teleconference Details

Tuesdays, 11:00am Eastern US (Boston) time zone
Zakim (W3C teleconference bridge).
Dial-In #: +1.617.761.6200 (Cambridge, MA)
VoIP address: sip:zakim@voip.w3.org
Participant Access Code: 4257 ("HCLS")
IRC: irc.w3.org port 6665 channel #hcls

Screen sharing (when used) is courtesy of Claude Nanjo. It is only used for screen sharing -- not for the teleconference bridge. The W3C teleconference bridge (above) will still be used even when we are using GoToMeeting for screen sharing. To join the screen sharing, browse to:

https://global.gotomeeting.com/join/157514853
Access Code: 157-514-853

See also:

Upcoming

  1. Github page on RDF
  2. Discuss Yosemite Project. Add who is doing what?
  3. Discuss use cases (when Guoqian is available)
  4. Valuesets in FHIR (Lloyd)
    1. See also Tony Mallia's latest Terminology Binding draft

Work Projects

Moved to RDF for Semantic Interoperability home page