Raised Issues

Apply the following changes to selected issues:

There are 43 raised issues listed in the system.

ID State Title Raised on Product Open Actions
ISSUE-1 (edit) RAISED Fhir modifying extensions and monotonicity 2014-12-02 0
ISSUE-2 (edit) RAISED How to handle fhir versioning? should fhir ontology track the fhir versions? how do we know which version the instance data corresponds to? 2015-01-27 0
ISSUE-3 (edit) RAISED How to represent coding system, code and version as round-trippable uris? 2015-03-03 0
ISSUE-5 (edit) RAISED What rdf mechanism to use for lists/sequences? 2015-04-01 0
ISSUE-8 (edit) RAISED If we treat observation.code as an instance of a class, should that class represent the disease itself or a *description* of the disease? 2015-04-22 0
ISSUE-10 (edit) RAISED How to represent codeableconcept, coding and code? should all three be constraints on a common rdf type? 2015-04-28 0
ISSUE-11 (edit) RAISED Should we define uri template guidance for vocabularies (coding system + code)? 2015-06-09 0
ISSUE-12 (edit) RAISED Should we ask fhir to define canonicalization to be use prior to signatures, to make uris absolute and put elements in predictable order? 2015-06-09 0
ISSUE-13 (edit) RAISED What namespace to use for fhirrdf:index ? 2015-06-24 0
ISSUE-14 (edit) RAISED Should our fhir rdf ontology restrict coding.text to cardinality 0, which would prevent that ontology from being usable with fhir rdf that is combined with non-fhir rdf data that adds a text property? 2015-08-11 0
ISSUE-15 (edit) RAISED Should a valueset be modeled as a union of concept classes, or as a set of concept individuals? 2015-08-25 0
ISSUE-16 (edit) RAISED Should fhir:reference.reference->value be a string or an rdf uri node? 2015-12-01 0
ISSUE-17 (edit) RAISED Should the rdf:types be explicit on the wire or inferred? 2015-12-01 0
ISSUE-18 (edit) RAISED How to determine the base uri for a fhir document, and is it round trippable? 2016-01-19 0
ISSUE-19 (edit) RAISED Should shex be a reference implementation or a schema? 2016-02-16 0
ISSUE-20 (edit) RAISED How to represent fhir:datetime values? three different types? plain xsd:strings? 2016-03-01 0
ISSUE-21 (edit) RAISED Should a type arc be required for the target of a reference? 2016-04-19 0
ISSUE-22 (edit) RAISED Should a type arc be allowed for the target of a reference? 2016-04-19 0
ISSUE-23 (edit) RAISED Do we need a fhir:reference (name tbd) whose value is an rdf uri of the referent? 2016-04-26 0
ISSUE-24 (edit) RAISED Must absolute and relative references be round tripped as is? 2016-04-26 0
ISSUE-25 (edit) RAISED Concept code uri: should we have one? what should it be? 2016-05-17 0
ISSUE-26 (edit) RAISED What should the fhir:link target be in the shex? 2016-05-17 0
ISSUE-27 (edit) RAISED Can we use an rdf iri when the fhir spec says xs:anyuri? 2016-05-17 0
ISSUE-28 (edit) RAISED What are the exact semantics of multiple codings for an observation.code? 2016-05-24 0
ISSUE-29 (edit) RAISED How to handle fhir slicing? 2016-05-31 0
ISSUE-30 (edit) RAISED How to handle elementdefinition.type.aggregation 2016-05-31 0
ISSUE-31 (edit) RAISED How to handle fhir pattern[x] 2016-05-31 0
ISSUE-32 (edit) RAISED How to handle fhir min/max value? 2016-05-31 0
ISSUE-33 (edit) RAISED How to handle elementdefinition.defaultvalue[x]? 2016-05-31 0
ISSUE-34 (edit) RAISED How to handle elementdefinition.meaningwhenmissing ? 2016-05-31 0
ISSUE-35 (edit) RAISED How to handle elementdefinition.fixed[x] ? 2016-05-31 0
ISSUE-36 (edit) RAISED How to handle required/extensible/example in shex? 2016-05-31 0
ISSUE-37 (edit) RAISED Should we try to unify the treatment of extensions with regular resources? 2016-06-21 0
ISSUE-38 (edit) RAISED How to handle modifiers? 2016-06-21 0
ISSUE-39 (edit) RAISED Define canonical fhir rdf https://github.com/w3c/hcls-fhir-rdf/issues/34 2016-08-23 0
ISSUE-40 (edit) RAISED Fhir rdf ontology urls do not resolve 2017-03-28 0
ISSUE-41 (edit) RAISED Protege does not show bnodes 2017-03-28 0
ISSUE-42 (edit) RAISED Need to clean up the hcls-fhir-rdf github 2017-07-11 0
ISSUE-43 (edit) RAISED Talk with rob hausam about whether to publish this on the fhir site or put it in a terminology service 2017-07-11 0
ISSUE-44 (edit) RAISED How to handle gyear gyearmonth etc as datetime in owl 2017-08-01 0
ISSUE-45 (edit) RAISED Need to follow rector's guidance on handling valuesets in owl 2017-11-07 0
ISSUE-46 (edit) RAISED Is mime type application/json-ld still used? if not, need to take it out of the fhir spec 2017-11-07 0
ISSUE-47 (edit) RAISED Need to get code systems and valuesets back into fhir.ttl 2017-11-28 0

Raise an issue .

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: raised.html,v 1.1 2018/03/01 14:14:15 jean-gui Exp $