FHIR RDF Issues list

https://github.com/w3c/hcls-fhir-rdf/issues

https://github.com/w3c/hcls-fhir-rdf/issues/37

Discussed here:

https://www.w3.org/2016/09/06-hcls-minutes.html

And then with grahame here:

http://wiki.hl7.org/index.php?title=ITS_RDF_Concall_Minutes_20160906

<ericP> issue-37

<trackbot> issue-37 -- Should we try to unify the treatment of extensions with regular resources? -- raised

<trackbot> http://www.w3.org/2014/HCLS/track/issues/37

<ericP> no trackbot, the *other* issue 37

dbooth: no, not the trackbot issues list. we're using the github issues list

eric: On which cases are we expecting a type? Any that have a parseable URI?
... Here's the problem: suppose someone sets up a server that *accidentally* looks like parseable URIs.
... The type is provided by the import mechanism. The importer will make a best effort to accurately type references, noting that non-FHIR-server resources may erroneously typable FHIR resources.

<ericP> http://w3c.github.io/hcls-fhir-rdf/spec/

<scribe> ACTION: Eric to add guidance to the FHIR RDF spec doc (at W3C) that if someone erroneously creates a ref URI that parses as though it indicates the type, but does not match the type, then validation may be wrong [recorded in http://www.w3.org/2016/10/11-hcls-minutes.html#action01]

<trackbot> Created ACTION-70 - Add guidance to the fhir rdf spec doc (at w3c) that if someone erroneously creates a ref uri that parses as though it indicates the type, but does not match the type, then validation may be wrong [on Eric Prud'hommeaux - due 2016-10-18].

<ericP> TODO in the FHIR RDF spec

https://github.com/w3c/hcls-fhir-rdf/issues/31

https://github.com/w3c/hcls-fhir-rdf/issues/30

<scribe> ACTION: Eric to add suitable verbiage to the FHIR RDF spec at W3C, about "A type arc for the referent should be used when available. Validation is only defined when there is a discriminating type arc on the referent. If a type arc is implied by the reference URI, then it should be used for validation. However, users should be aware that if the reference URI implies a misleading type, then validation may fail and the RDF graph may be interpreted improperly." [recorded in http://www.w3.org/2016/10/11-hcls-minutes.html#action02]

<trackbot> Created ACTION-71 - Add suitable verbiage to the fhir rdf spec at w3c, about "a type arc for the referent should be used when available. validation is only defined when there is a discriminating type arc on the referent. if a type arc is implied by the reference uri, then it should be used for validation. however, users should be aware that if the reference uri implies a misleading type, then validation may fail and

<trackbot> ... the rdf graph may be interpreted improperly." [on Eric Prud'hommeaux - due 2016-10-18].

ShEx Specification

<ericP> ShEx Specification

eric: eyeballs on the ShEx spec would be helpful

ADJOURNED

============== 5PM CALL CANCELED TODAY ==============

This is scribe.perl Revision: 1.148  of Date: 2016/10/11 12:55:14  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: dbooth
Inferring Scribes: dbooth

WARNING: No "Present: ... " found!
Possibly Present: dbooth eric ericP hcls https joined left trackbot
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

        <amy> Present+

Found Date: 11 Oct 2016
Guessing minutes URL: http://www.w3.org/2016/10/11-hcls-minutes.html
People with action items: eric