This is a weekly teleconference for anyone interested
in contributing to the Yosemite Project[1]. Its purpose
is to coordinate activities such as roadmap refinement,
standards development, webinar planning, outreach and
technical demonstrations that advance the Yosemite
Project mission.
All part
See my reply to Grahame.
*Lloyd McKenzie*, P.Eng.
Senior Consultant, Information Technology Services
Gevity Consulting Inc.
E: lmcken...@gevityinc.com
M: +1 587-334-1110 <1-587-334-1110>
W: gevityinc.com
*GEVITY**Informatics for a healthier world *
CONFIDENTIALITY – This communication is conf
Attached is the OWL you provided. Maybe there was something else?
Tony
From: Lloyd McKenzie [mailto:ll...@lmckenzie.com]
Sent: Thursday, July 16, 2015 7:03 PM
To: Anthony Mallia
Cc: David Booth; w3c semweb HCLS; i...@lists.hl7.org
Subject: Re: CodeableThingy
In the OWL XML I provided, I used sub
In the OWL XML I provided, I used subclass - because I know that works.
You're welcome to experiment with equivalent class.
*Lloyd McKenzie*, P.Eng.
Senior Consultant, Information Technology Services
Gevity Consulting Inc.
E: lmcken...@gevityinc.com
M: +1 587-334-1110 <1-587-334-1110>
W: gevityi
The abstract superclass was not in the proposed scheme. The structure is
containment rather like the existing FHIR CodeableConcept, Coding, code
structure except that everything becomes what is equivalent to the
CodeableConcept.
If we want an abstract superclass then we have to change the approa
Thanks David.
This is a valuable support.
I noticed also that I had not YET introduced this info in our HL7 ITS RDF WG and after the holidays I put this in priorities.
The bigger the community will be the chance to cover every one's needs will be.
Kind Regards,
Marc Twagirumukiza | Agfa HealthCar
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: lmck
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
FYI. I just noticed that this never got forwarded to the HCLS and ITS
lists.
Forwarded Message
Subject:health.schema.org Extension
Resent-Date:Fri, 12 Jun 2015 11:28:37 +
Resent-From:public-sche...@w3.org
Date: Fri, 12 Jun 2015 13:27:46 +0200
From: Marc
