14:55:52 <RRSAgent> RRSAgent has joined #hcls
14:55:52 <RRSAgent> logging to https://www.w3.org/2022/07/28-hcls-irc
14:55:57 <dbooth> rrsagent, make logs public
14:56:05 <dbooth> Meeting: FHIR RDF
14:56:10 <dbooth> Chair: David Booth
15:08:02 <dbooth> Topic:  Open
15:08:02 <dbooth> Properties with both scalar and object range #102
15:13:26 <dbooth> jim: Would option 2 also address the RDF list issue?
15:14:28 <dbooth> ... Could maybe offer tooling to convert from OWL friendly version to SPAREQL friendly version
15:14:49 <dbooth> DBooth: Preferences?
15:15:19 <dbooth> ... most in favor of #5.
15:16:49 <dbooth> dbooth: Would be strongly against having two versions
15:17:55 <dbooth> AGREED: option 5, not hoist scalars (same as R4)
15:20:02 <dbooth> eric: Should also bring awareness to the larger sem web coimmunity about this issue.
15:20:53 <dbooth> dbooth: I think it's a flaw in the OWL to discourage that.
15:21:58 <dbooth> This closes both #102 and #77
15:24:21 <dbooth> This also closes #103
15:29:49 <dbooth> Topic: How should modifier extensions be handled in RF? #93
15:29:55 <dbooth> https://github.com/w3c/hcls-fhir-rdf/issues/93
15:31:30 <dbooth> eric: Without hoisting, if wwe rename properties that have modifier ext by giving them a leading underbar, then we take care of the backbone element and scalar case.
15:32:28 <dbooth> ACTION: Dbooth to propose options
15:33:12 <dbooth> Topic: Issue 69: Shorten dot-compound property names?
15:34:46 <dbooth> dbooth: Not aware of any problems.  Implemented in the playground.
15:36:24 <dbooth> eric: FHIR folks are doing more to ensure that property names have a consistent meaning.
15:37:09 <dbooth> dbooth: And without hoisting, everything is an object property anyway.
15:39:23 <dbooth> Topic:  We should not use fhir:value for non-hoisted scalar properties #104
15:39:31 <dbooth> We could use rdf:value instead.  That's what it was made for.   Jim: That would not work with OWL.
15:40:24 <dbooth> eric: But you cannot do inference with literals anyway.
15:41:24 <dbooth> ... I tried If the code is 123435, then some inference, but could not get it working.
15:41:36 <dbooth> jim: You have to make a class expression
15:44:43 <dbooth> ACTION: jim to look into whether rdf:value would work instead of fhir:value
15:45:10 <dbooth> Topic: Issue 76: Ordered lists
15:45:48 <dbooth> jim: PR almost ready for changes to parse the list
15:46:17 <dbooth> ... Caveat: If you apply owl annotations to those axioms, those annotations don't get parsed.  That would be hard to solve.
15:46:33 <dbooth> dbooth: Is anyone likely to do that?
15:46:47 <dbooth> jim: It won't be in our FHIR output with RDF lists.
15:48:05 <dbooth> ... It would be weird to do.
15:48:24 <dbooth> ... It would involve reifying the list axiom.
15:49:21 <dbooth> dbooth: Do we still want to go ahead w RDF lists?
15:49:38 <dbooth> eric: Still keen on using lists.
15:50:43 <dbooth> jim: Last week I tried out using non-RDF property names for first and rest, and it worked.
15:51:11 <dbooth> dbooth: We could potentially publicize that as a workaround for folks who are bothered by RDF lists.
15:55:35 <dbooth> ACTION: jim to try OWL example that uses a scalar value
15:57:09 <dbooth> Topic: Meet also on Tuesdays, same time?
15:57:12 <dbooth> eric: Maybe
15:57:16 <dbooth> rob: Probably
15:57:24 <dbooth> jim: Can do the second two
15:57:47 <dbooth> houcemeddine: okay for me.
15:58:10 <dbooth> Topic: Issue 95: References lack a type arc
16:03:15 <dbooth> dbooth: Grahame pointed out that this would be a breaking change to make the "type" property required in the case of an absolute URL reference, so it isn't a change we can make.  And we can live with it anyway.
16:03:55 <dbooth> eric: This would mostly affect validation of local internal hospital networks.
16:04:18 <dbooth> dbooth: Close the issue with no change?
16:04:46 <dbooth> eric: Close with a note saying we do not validate cases with absolute URLs beyond what FHIR requires for validation.
16:06:24 <dbooth> AGREED: Close #95 with no change.
16:06:50 <dbooth> ADJOURNED
16:09:21 <dbooth> i/Topic: Issue 95/ACTION: DBooth to announce additional meetings
16:09:29 <dbooth> rrsagent, draft minutes
16:09:29 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/28-hcls-minutes.html dbooth
16:12:21 <dbooth> s/Topic:  Open//
16:12:40 <dbooth> s/Properties with both scalar and object rang/Topic: Properties with both scalar and object rang/
16:12:53 <dbooth> rrsagent, draft minutes
16:12:53 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/28-hcls-minutes.html dbooth
16:13:59 <dbooth> Present: Jim Balhoff, Houcemeddine, EricP, Rob Hausam, David Booth
16:14:02 <dbooth> rrsagent, draft minutes
16:14:02 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/28-hcls-minutes.html dbooth
16:14:22 <dbooth> Regrets: Gaurav Vaidya
16:14:23 <dbooth> rrsagent, draft minutes
16:14:23 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/28-hcls-minutes.html dbooth
16:26:51 <dbooth> i/We should not use fhir:value for non-hoisted/AGREED: Shorten property names.
16:27:20 <dbooth> rrsagent, draft minutes
16:27:20 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/28-hcls-minutes.html dbooth
16:39:12 <dbooth> s/handled in RF/handled in RDF/
16:39:15 <dbooth> rrsagent, draft minutes
16:39:15 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/28-hcls-minutes.html dbooth
16:40:59 <dbooth> i/Without hoisting, if wwe/eric: We want to prevent a FHIR processor from not noticing the modifier ext and processing the data naively.
16:41:07 <dbooth> rrsagent, draft minutes
16:41:07 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/28-hcls-minutes.html dbooth