- From: Lloyd McKenzie <lloyd@lmckenzie.com>
- Date: Thu, 16 Jul 2015 17:52:26 -0400
- To: David Booth <david@dbooth.org>
- Cc: w3c semweb HCLS <public-semweb-lifesci@w3.org>, "its@lists.hl7.org" <its@lists.hl7.org>
- Message-ID: <CAJ860JJ0-yHyg5S9sqp2Ur7BAgDgG0XT_nm-Z13zDV73tLKkEA@mail.gmail.com>
Let's not worry about naming until we've verified whether an abstract superclass approach is in fact necessary. I'd like to keep the FHIR terms as part of the name just to avoid confusion. *Lloyd McKenzie*, P.Eng. Senior Consultant, Information Technology Services Gevity Consulting Inc. E: lmckenzie@gevityinc.com M: +1 587-334-1110 <1-587-334-1110> W: gevityinc.com *GEVITY**Informatics for a healthier world * CONFIDENTIALITY – This communication is confidential and for the exclusive use of its intended recipients. If you have received this communication by error, please notify the sender and delete the message without copying or disclosing it*.* NOTE: Unless explicitly stated otherwise, the opinions and positions expressed in this e-mail do not necessarily reflect those of my employer, my clients nor the organizations with whom I hold governance positions On Thu, Jul 16, 2015 at 5:46 PM, David Booth <david@dbooth.org> wrote: > I would be inclined to try to align more with existing FHIR naming than > SNOMED-CT naming. Since we're not using an abstract superclass approach, > how about calling it a fhir:CodeableConcept? > > David > > On 07/15/2015 07:14 PM, Anthony Mallia wrote: > >> We need to name CodeableThingy and other Thingy's which were >> temporary names. Here is a suggestion of how the structure might be >> named. Reminder that even if the original FHIR XML element was a >> CodeableConcept, Coding or code, when in the RDF space it will always >> be the CodeableThingy sparsely populated appropriately. >> >> Here is a proposed set of names that aligns somewhat with the SNOMED >> CT names. fhir:CodeableThingy becomes a fhir:Concept (this is >> distinct from the fhir:ValueSet.Concept) fhir:CodingThingy becomes a >> fhir:Term – a Concept represented in a specific terminology system >> fhir:codeThingy becomes a fhir:Term.Code thereby internally declared >> to Term. All the object properties of fhir:Term have ranges of >> Term.Code, Term.Display, Term.System, Term.Version and Term.Primary. >> This allows greater control of the classes as opposed to the general >> use of fhir:URI and fhir:String. >> >> fhir:Concept.term [ rdf:type fhir:Term; fhir:Term.system [ a >> fhir:Term.System ; “fhir:value >> http://example.org/local”^^fhir:uri-primitive ] ; fhir:Term.code [ a >> fhir:Term.Code ; fhir:value "admin"^^fhir:code-primitive ] ; >> fhir:Term.display [ a fhir:Term.Display ; fhir:value >> "Admin"^^fhir:string-primitive ] ; ]; >> >> >> Tony Mallia EDMOND SCIENTIFIC COMPANY (ESC) >> >> >> >> -----Original Message----- From: David Booth >> [mailto:david@dbooth.org] Sent: Tuesday, July 14, 2015 1:03 PM To: >> w3c semweb HCLS; its@lists.hl7.org Cc: Lloyd McKenzie Subject: Fwd: >> Re: CodeableThingy >> >> >> We discussed this on today's call: >> http://www.w3.org/2015/07/14-hcls-minutes.html#item06 >> >> Tony made some good progress on adding it in to his side-by-side >> example document: >> >> http://wiki.hl7.org/index.php?title=File:FHIR_RDF_Sample_side_by_side_comparisons.pdf >> >> >> >> A couple of questions remained, and were recorded as action items to > figure out: > >> >> [NEW] ACTION: Rob to check with Lloyd about whether someone can >> define a Code, specifying a new coding system URI in [recorded in >> http://www.w3.org/2015/07/14-hcls-minutes.html#action03] >> >> [NEW] ACTION: Tony to ask lloyd about attaching a class breadcrumb to >> a CodeableThingy instance to indicate what FHIR form it was >> originally [recorded in >> http://www.w3.org/2015/07/14-hcls-minutes.html#action02] >> >> Thanks, David Booth >> >> -------- Forwarded Message -------- Subject: Re: CodeableThingy >> Date: Tue, 14 Jul 2015 07:28:44 -0400 From: Lloyd McKenzie >> <lloyd@lmckenzie.com> Reply-To: Lloyd McKenzie >> <lloyd@lmckenzie.com> To: Grahame Grieve >> <grahame@healthintersections.com.au> CC: HL7 ITS >> <its@lists.hl7.org> >> >> >> >> Well, what I had actually proposed (and know how to make work) is >> this: <SubClassOf> <Class abbreviatedIRI="hl7:CodeableConcept"/> >> <Class abbreviatedIRI="hl7:CodeableThingy"/> </SubClassOf> >> <SubClassOf> <Class abbreviatedIRI="hl7:Coding"/> <Class >> abbreviatedIRI="hl7:CodeableThingy"/> </SubClassOf> <SubClassOf> >> <Class abbreviatedIRI="hl7:Coding"/> <ObjectExactCardinality >> cardinality="1"> <ObjectProperty >> abbreviatedIRI="hl7:CodeableThingy.coding"/> >> </ObjectExactCardinality/> </SubClassOf> <SubClassOf> <Class >> abbreviatedIRI="hl7:Coding"/> <ObjectMaxCardinality cardinality="0"> >> <ObjectProperty abbreviatedIRI="hl7:CodeableThingy.text"/> >> </ObjectMaxCardinality/> </SubClassOf> <SubClassOf> <Class >> abbreviatedIRI="hl7:Code"/> <Class >> abbreviatedIRI="hl7:CodeableThingy"/> </SubClassOf> <SubClassOf> >> <Class abbreviatedIRI="hl7:Code"/> <ObjectExactCardinality >> cardinality="1"> <ObjectProperty >> abbreviatedIRI="hl7:CodeableThingy.coding"/> >> </ObjectExactCardinality/> </SubClassOf> <SubClassOf> <Class >> abbreviatedIRI="hl7:Coding"/> <ObjectMaxCardinality cardinality="0"> >> <ObjectProperty abbreviatedIRI="hl7:CodeableThingy.text"/> >> </ObjectMaxCardinality/> </SubClassOf> <SubClassOf> <Class >> abbreviatedIRI="hl7:Coding"/> <ObjectMaxCardinality cardinality="0"> >> <ObjectProperty abbreviatedIRI="hl7:CodeableThingy.text"/> >> </ObjectMaxCardinality/> </SubClassOf> <SubClassOf> <Class >> abbreivatedIRI="hl7:Coding"/> <ObjectAllValuesFrom> <ObjectProperty >> abbreviatedIRI="hl7:CodeableThingy.coding"/> <ObjectMaxCardinality >> cardinality="0"> <ObjectProperty >> abbreviatedIRI="hl7:CodingThingy.display"/> </ObjectMaxCardinality> >> </ObjectAllValuesFrom> </SubClassOf> <SubClassOf> <Class >> abbreivatedIRI="hl7:Coding"/> <ObjectAllValuesFrom> <ObjectProperty >> abbreviatedIRI="hl7:CodeableThingy.coding"/> <ObjectMaxCardinality >> cardinality="0"> <ObjectProperty >> abbreviatedIRI="hl7:CodingThingy.primary"/> </ObjectMaxCardinality> >> </ObjectAllValuesFrom> </SubClassOf> <EquivalentClasses> <Class >> abbreviatedIRI="hl7:CodeableThingy"/> <ObjectUnionOf> <Class >> abbreviatedIRI="hl7:CodeableConcept"/> <Class >> abbreviatedIRI="hl7:Coding"/> <Class abbreviatedIRI="hl7:Code"/> >> </ObjectUnionOf> </EquivalentClasses> >> >> Whether we can make the whole thing work with equivalent classes, I'm >> not sure, but happy for Tony to try :> >> >> *Lloyd McKenzie*, P.Eng. Senior Consultant, Information Technology >> Services Gevity Consulting Inc. >> >> E: lmckenzie@gevityinc.com <mailto:lmckenzie@gevityinc.com> M: +1 >> 587-334-1110 <tel:1-587-334-1110> W: gevityinc.com >> >> <http://gevityinc.com/> >> >> *GEVITY **/Informatics for a healthier world /* >> >> CONFIDENTIALITY – This communication is confidential and for the >> exclusive use of its intended recipients. If you have received this >> communication by error, please notify the sender and delete the >> message without copying or disclosing it*.* >> >> NOTE: Unless explicitly stated otherwise, the opinions and positions >> expressed in this e-mail do not necessarily reflect those of my >> employer, my clients nor the organizations with whom I hold >> governance positions >> >> >> On Tue, Jul 14, 2015 at 5:30 AM, Grahame Grieve >> <grahame@healthintersections.com.au >> <mailto:grahame@healthintersections.com.au>> wrote: >> >> Lloyd >> >> I don't really understand any of this, because I don't know what you >> mean by 'is an equivalent class of'. Is this an actual is-a >> statement? or just something that means whatever you want it to >> mean? >> >> Class CodeableConcept is an equivalent class of CodeableThingy >> >> Class Coding is an equivalent class of CodeableThingy where there can >> be only 0..1 CodingThingy.coding and 0..0 CodingThingy.text >> >> Class code is an equivalent class of CodeableThingy where there is >> 1..1 CodingThingy.coding and 0..0 CodingThingy.text and the >> CodingThingy.coding has 0..0 CodeableThingy.display and 0..0 >> CodeableThingy.primary >> >> >> Grahame >> >> >> >> On Thu, Jul 9, 2015 at 2:02 AM, Lloyd McKenzie <lloyd@lmckenzie.com >> <mailto:lloyd@lmckenzie.com>> wrote: >> >> From our discussion today >> >> *Lloyd McKenzie*, P.Eng. Senior Consultant, Information Technology >> Services Gevity Consulting Inc. >> >> E: lmckenzie@gevityinc.com <mailto:lmckenzie@gevityinc.com> M: +1 >> 587-334-1110 <tel:1-587-334-1110> W: gevityinc.com >> >> <http://gevityinc.com/> >> >> *GEVITY **/Informatics for a healthier world /* >> >> CONFIDENTIALITY – This communication is confidential and for the >> exclusive use of its intended recipients. If you have received this >> communication by error, please notify the sender and delete the >> message without copying or disclosing it*.* >> >> NOTE: Unless explicitly stated otherwise, the opinions and positions >> expressed in this e-mail do not necessarily reflect those of my >> employer, my clients nor the organizations with whom I hold >> governance positions >> >> >> >> *********************************************************************************** >> >> >> Manage your subscriptions <http://www.HL7.org/listservice> | > >> View the archives <http://lists.HL7.org/read/?forum=its> | >> Unsubscribe >> >> < >> http://www.HL7.org/tools/unsubscribe.cfm?email=grahame@healthintersections.com.au&list=its >> > >> >> >> | Terms of use > >> <http://www.HL7.org/myhl7/managelistservs.cfm?ref=nav#listrules> >> >> >> >> >> -- ----- http://www.healthintersections.com.au / >> grahame@healthintersections.com.au >> <mailto:grahame@healthintersections.com.au> / +61 411 867 065 >> <tel:%2B61%20411%20867%20065> >> >> >> >> *********************************************************************************** >> >> >> Manage your subscriptions <http://www.HL7.org/listservice> | View the > archives <http://lists.HL7.org/read/?forum=its> | Unsubscribe < > http://www.HL7.org/tools/unsubscribe.cfm?email=david@dbooth.org&list=its> > >> | Terms of use >> <http://www.HL7.org/myhl7/managelistservs.cfm?ref=nav#listrules> >> >> >> >> >> > > *********************************************************************************** > Manage subscriptions - http://www.HL7.org/listservice > View archives - http://lists.HL7.org/read/?forum=its > Unsubscribe - > http://www.HL7.org/tools/unsubscribe.cfm?email=lloyd@lmckenzie.com&list=its > Terms of use - > http://www.HL7.org/myhl7/managelistservs.cfm?ref=nav#listrules >
Received on Thursday, 16 July 2015 21:53:16 UTC