14:59:03 RRSAgent has joined #hcls 14:59:03 logging to https://www.w3.org/2022/04/07-hcls-irc 14:59:09 rrsagent, make logs public 14:59:16 Meeting: FHIR RDF 14:59:19 Chair: David Booth 15:04:01 Topic: Concept IRIs 15:12:21 dbooth: I think eric's position is that we should allow creativity in the design of concept IRIs, which would require that things like slashes get passed through without percent encoding. 15:12:27 eric: yes. 15:13:26 dbooth: I have sympathy for supporting creativity, but also worry that the designers of these terminologies will probably not be thinking about how their codes will be turned into IRIs. 15:14:01 eric: We could define two different algorithms, with a flag for each stem IRI, that says which algorithm to use. 15:16:53 dbooth: Confirmed that a hash cannot appear in a fragid. 15:18:08 eric: We could more fully parameterize the algorithm depending on what part of the IRI it falls into: path, search parameter, fragid, etc. 15:19:52 eric: SNOMED has a hierarchy, eg a procedure or an abstract value or reference range -- they all have their own places in the SNOMED hierarchy. If Kent Spackman did it again, he could take that into account. 15:23:09 gaurav: If codesystem (or a new property that goes with stem IRI) tells you how to validate the code, then that will tell you how we need to encode it? 15:23:47 ... E.g., if SNOMED says that slash is allowed in codes, then we can pass it through without encoding it. 15:24:09 ... For most wiki codes, they give a regex and a template. 15:26:50 gaurav: For FHIR codesystem, you can define a filter to only included certain codes. 15:27:22 ... They also allow regex to filter them. 15:28:01 ... And you can have multiple filters, and 8-9 operators and they don't expect implementers to implement them all. 15:30:08 dbooth: Exactly which chars are we concerned about? Only slash, and always encode hashes? Or are there other other chars we might want to pass through? 15:30:55 eric: hash, question mark, ampersand, semicolon, equals, slash. 15:32:57 eric: For SNOMED you'd want to encode everything, because if somebody used a postcoordinated code w comments in it, that should be percent encoded. 15:34:52 dbooth: Is there other data that would help us decide? Look at what chars are used in codes? 15:35:51 gaurav: UCUM has slashes, square brackets, asterisk, percent (for percentages), curly brackets. 15:37:47 dbooth: That's an example of slashes clearly not being used for hierarchy -- they're used for division. 15:38:48 eric: There's also two schools of though about where to put units -- into the quoted part of the RDF term, vs into the datatype. 15:39:57 UCUM examples: 15:39:58 [[ 15:39:59 h 15:39:59 U 15:39:59 ug 15:39:59 [IU] 15:40:00 mg/m2 15:40:04 ml/h 15:40:06 kcal 15:40:08 cal/mL 15:40:10 mL/d 15:40:12 mL/h 15:40:14 cal/[foz_us] 15:40:16 [foz_us] 15:40:18 {scoop} 15:40:20 {score} 15:40:22 ]] 15:48:03 dbooth: I think we need more evidence about what chars are used in codes. 15:48:26 eric: Could have a conservative algo and a liberal algo. 15:50:06 gaurav: I like that idea. But an example had old codes that were no longer resolvable, eg LOINC code: LA6721-0 15:50:59 ... Could say that this algo only applies if the code matches ##### (all digits) 15:59:13 ACTION: Gaurav to find codes in more terminologies to see what chars they use. 15:59:38 dagmar: In our work we should always end a stem IRI with slash or hash. 16:01:08 Present: David Booth, Gaurav Vaidya, Dagmar, EricP 16:01:12 rrsagent, draft minutes 16:01:12 I have made the request to generate https://www.w3.org/2022/04/07-hcls-minutes.html dbooth 16:39:13 ADJOURNED 16:39:16 rrsagent, draft minutes 16:39:16 I have made the request to generate https://www.w3.org/2022/04/07-hcls-minutes.html dbooth