Minutes from FHIR RDF call (Aug 26): Issue 77: Primitive properties and extensions

Minutes from Aug 26 call are here and in plain text below:
https://www.w3.org/2021/08/26-hcls-minutes.html

Please note we need your input and ideas about how best to resolve issue 
77: How should extensions be represented in R5, both for primitive 
datatypes and for objects?  Please post new ideas or comments on github:
https://github.com/w3c/hcls-fhir-rdf/issues/77

Thanks,
David Booth

         -------------------------------------------------

    [1]W3C

       [1] https://www.w3.org/

                              – DRAFT –
                                 FHIR RDF

26 August 2021

    [2]IRC log.

       [2] https://www.w3.org/2021/08/26-hcls-irc

Attendees

    Present
           David Booth, Emily Pfaff, EricP, Gopi, Jim Balhoff

    Regrets
           -

    Chair
           David Booth

    Scribe
           dbooth

Contents

     1. [3]FHIR build process
     2. [4]Issue 77 - How should extensions be represented in R5,
        both for primitive datatypes and for objects?

Meeting minutes

   FHIR build process

    david: The FHIR build process generates the entire spec and all
    of the examples, in XML, JSON and Turtle. Right now the Turtle
    is generated by Grahame's custom code, and it's pretty to look
    at -- very readable. If we also generate RDF via JSON-LD 1.1,
    then we can validate against what Grahame's code produces.

    emily: What about prettifiying the JSON-LD generated RDF?

    eric: Having multiple implementations gives more variety of
    tools and provides more sanity checking.

    david: don't know how we could eaisily do prettifying.

    eric: We'd have to write our own, esp to keep the same order of
    properties, but would end up being as complicated as the
    current generation in the build process.

    emily: Does HAPI play a role in the build process today?

    eric: I think the HAPI libraries used in the build process.

   Issue 77 - How should extensions be represented in R5, both for
   primitive datatypes and for objects?

    david: I pulled out modifier extensions to issue 93.

    eric: I think we need to be aware of modifier ext in
    considering regular ext.

    eric: for modifier, want to break the graph, but use the same
    structure for the extension.
    … We have a coherent model, but not so user friendly. Mostly
    extensions are not used, except for confidence levels and
    saying the something is not present.
    … For modifier ext, should change the name of the predicate.
    … Goal in simplifying common use case, is that the JSON-LD we
    emit does not require post-processing. JSON-LD cannot invent
    extra levels of indirection. In the common case, if we got rid
    of the stand-off, we'd be able to do most of the work in
    JSON-LD without pre/post processors, until we hit extensions.

    (Reviewed options in [5]https://github.com/w3c/hcls-fhir-rdf/
    issues/77 )

       [5] https://github.com/w3c/hcls-fhir-rdf/issues/77

    david: Please review the options, suggest improvements or new
    ideas, and think about which options you like and which you
    don't like.

    ADJOURNED


     Minutes manually created (not a transcript), formatted by
     [6]scribe.perl version 136 (Thu May 27 13:50:24 2021 UTC).

       [6] https://w3c.github.io/scribe2/scribedoc.html

Received on Tuesday, 31 August 2021 02:51:01 UTC