IRC log of hcls on 2022-05-12

Timestamps are in UTC.

14:55:20 [RRSAgent]
RRSAgent has joined #hcls
14:55:20 [RRSAgent]
logging to https://www.w3.org/2022/05/12-hcls-irc
14:55:27 [dbooth]
rrsagent, make logs public
14:55:53 [dbooth]
Chair: David Booth
14:55:56 [dbooth]
Meeting: FHIR RDF
15:03:15 [dbooth]
Regrets: Jim Balhoff
15:03:36 [dbooth]
Topic: HL7 meeting report
15:06:38 [dbooth]
dbooth: Meeting went well. They were interested in the Concept IRI idea, but didn't have any feedback on it.
15:08:49 [dbooth]
... I didn't sense any thought of pulling the plug on FHIR RDF.
15:09:13 [dbooth]
... Small group, only HL7 ITS chairs and Vassil Paytchev(sp?) from Epic.
15:09:51 [dbooth]
Topit: RDF Lists
15:10:16 [dbooth]
gaurav: Jim is working on a PR for the OWL API group.
15:10:25 [dbooth]
s/Topit/Topic/
15:10:45 [dbooth]
Topic: Concept IRIs
15:11:13 [dbooth]
gaurav: Looking for example codes that might be hierarchical. Found Clinical Care Classification.
15:11:51 [dbooth]
... Example: C.06.1.3
15:12:02 [dbooth]
https://careclassification.org/online-code-builder-1/
15:12:37 [dbooth]
gaurav: c= cardiac
15:12:58 [dbooth]
... 06 = cardio vascular alteration
15:13:34 [dbooth]
... .1 is blood pressure alteration
15:13:43 [dbooth]
... 3 is expected outcome
15:14:17 [dbooth]
gaurav: Another example I found: https://www.hcup-us.ahrq.gov/toolssoftware/ccs/CCSCategoryNames_FullLabels.pdf
15:14:24 [dbooth]
... 10.1.5.1 Calculus of kidney
15:15:44 [dbooth]
eric: If someone (re-)designed this for use in web space, they might use slashes.
15:16:30 [dbooth]
gaurav: Two more examples are like the dewey decimal system.
15:16:44 [dbooth]
... J82.83 Eosinophilic asthma
15:17:38 [dbooth]
eric: For a demo, we could take these and turn the dots into slashes.
15:19:59 [dbooth]
https://www.hcup-us.ahrq.gov/toolssoftware/ccs/ccs.jsp
15:20:41 [dbooth]
dbooth: This is convincing me that we should not try to support hierarchical URLs. I think it's natural for people to use things like dots as hierarchy separators.
15:21:30 [dbooth]
gaurav: Hierarchical could be in its own sub-proposal, for submission after the FHIR group accepts the basic idea.
15:23:04 [dbooth]
dbooth: Web servers are always free to interpret their URLs hierarchically however they want. They can treat dots as hierarchy if they choose, for example.
15:24:09 [dbooth]
AGREED: We will only do flat proposal first. Hierarchical would be a separate proposal later.
15:25:33 [dbooth]
ACTION: gaurav to update draft doc for only flat stem IRI
15:34:19 [ericP]
https://www.w3.org/2008/Talks/31-ASPE/xRIs.svg
15:34:40 [dbooth]
dbooth: Should the code be percent-encoded to be part of a URI or (more generally) a part of an IRI? I.e., which set of chars should be percent-encoded?
15:36:43 [dbooth]
example IRI (w Japanese/chinese): http://伝言.example/?user=أكرم&channel=R%26D
15:37:14 [dbooth]
... http://伝言.example/?user=أكرم&channel=R&D
15:38:13 [dbooth]
eric: First you punycode the domain name, then you URL encode the path. Then you have ambiguity: Need to know whether to decode the %26
15:40:53 [dbooth]
eric: Eg if a code were: كرم
15:43:53 [dbooth]
dbooth: Even if we pass that through, we'll still want to percent-encode things like slash, ampersand, equal, questionmark, etc.
15:46:21 [dbooth]
eric: But we only need to worry about escaping the ones that are enumerated.
15:46:39 [dbooth]
https://www.w3.org/TR/2012/REC-r2rml-20120927/#dfn-iri-safe
15:47:37 [dbooth]
eric: Propose that iunreserved be the set we do not percent-encode.
15:47:44 [dbooth]
iunreserved = ALPHA / DIGIT / "-" / "." / "_" / "~" / ucschar
15:48:21 [dbooth]
ucschar = %xA0-D7FF / %xF900-FDCF / %xFDF0-FFEF
15:48:42 [dbooth]
ucschar = %xA0-D7FF / %xF900-FDCF / %xFDF0-FFEF
15:49:56 [dbooth]
ucschar = %xA0-D7FF / %xF900-FDCF / %xFDF0-FFEF
15:49:57 [dbooth]
/ %x10000-1FFFD / %x20000-2FFFD / %x30000-3FFFD
15:49:57 [dbooth]
/ %x40000-4FFFD / %x50000-5FFFD / %x60000-6FFFD
15:49:57 [dbooth]
/ %x70000-7FFFD / %x80000-8FFFD / %x90000-9FFFD
15:49:58 [dbooth]
/ %xA0000-AFFFD / %xB0000-BFFFD / %xC0000-CFFFD
15:49:58 [dbooth]
/ %xD0000-DFFFD / %xE1000-EFFFD
15:51:19 [dbooth]
eric: everhthing that's reserved is below 7F. These are all A0 or above.
15:52:22 [dbooth]
dbooth: That looks good to me.
15:55:16 [dbooth]
gaurav: "
15:55:16 [dbooth]
The 17 planes can accommodate 1,114,112 code points. Of these, 2,048 are surrogates (used to make the pairs in UTF-16), 66 are non-characters, and 137,468 are reserved for private use, leaving 974,530 for public assignment."
15:56:58 [dbooth]
Topic: FHIR RDF Playground
15:58:01 [dbooth]
dbooth: People were impressed w the playground.
15:59:31 [dbooth]
eric: The process loads fhir defs, turns them into shexJ, then whenever it's asked for a @context file, it generates it on the fly from the shexJ, then uses the shexJ again for the rendering. That means I'm validating everything that I'm generating!
16:01:13 [dbooth]
... Downside is that changing to collections means you need lists of things: Instead of a codeable concept having N codings, it has a list of codings, which has an rdf:first and an rdf:rest that is either a list or a rdf:nil. That means I had to add a lot of lists: went from 1500 things to 2000 things.
16:01:26 [dbooth]
... i want to make that a primitive in shex, to make that unnecessary.
16:05:07 [dbooth]
s/1500 things/1500 shapes/
16:05:17 [dbooth]
s/2000 things/2000 shapes/
16:05:37 [dbooth]
Present: David Booth, EricP, Gaurav Vaidya
16:05:44 [dbooth]
rrsagent, draft minutes
16:05:44 [RRSAgent]
I have made the request to generate https://www.w3.org/2022/05/12-hcls-minutes.html dbooth