Stream: fhirpath
Topic: Trademark question - fhirpath.js
Paul Lynch (Nov 20 2018 at 15:11):
@Grahame Grieve I saw your blog post about the FHIR trademark. Does our open-source fhirpath.js library need one of those approvals?
I did see your note about going ahead and applying at www.fhir.org if uncertain, but the form I found includes the text "THE PERSON CLICKING THE <SUBMIT> BUTTON BELOW REPRESENTS AND WARRANTS ON BEHALF OF LICENSEE THAT S/HE IS AUTHORIZED TO SIGN CONTRACTS ON BEHALF OF, AND TO THEREBY BIND, LICENSEE. " I am certainly not that person, and it would probably require several people looking at it before that button could be clicked, so I thought I would ask here first.
Grahame Grieve (Nov 21 2018 at 00:27):
yes it does need one of those approvals
nicola (RIO/SS) (Dec 13 2018 at 09:05):
I think this should be simplified for fhir libraries - may be as part of FHIR foundation - aka recommended license etc. Pretty sure all fhirpath implementation will be called fhirpath :)
Grahame Grieve (Dec 13 2018 at 09:06):
sure. you just need to ask for approval. I can't simplify it any further
Grahame Grieve (Dec 13 2018 at 09:07):
I guess I could if the code is in a project in the FHIR foundation organization in github
Grahame Grieve (Dec 13 2018 at 09:07):
then there'd be no need to ask... I'll see if I can sort that
nicola (RIO/SS) (Dec 13 2018 at 09:08):
@Paul Lynch should we move our code base? :)
Grahame Grieve (Dec 13 2018 at 09:10):
let me know if you want me to create a project
Paul Lynch (Dec 13 2018 at 15:36):
I guess I could if the code is in a project in the FHIR foundation organization in github
That is an idea very much worth considering, and I am checking to see what NLM thinks about transferring ownership. Two questions for @Grahame Grieve
1) Would Nicola and I be given Admin privileges on the repository (so we could add collaborators as needed) or at least Write-level privileges (so we could merge pull requests)?
2) Would Health Samurai and NLM still be given credit (perhaps in the README) for their contributions?
Grahame Grieve (Dec 13 2018 at 20:10):
yes and yes
Grahame Grieve (Dec 13 2018 at 20:11):
some FHIR Foundation person would need to be admin but actual committers would also be admins
Grahame Grieve (Dec 13 2018 at 20:18):
also, would need to use a recognised open source license
Paul Lynch (Dec 13 2018 at 21:25):
also, would need to use a recognised open source license
Our current license is based on BSD: https://github.com/lhncbc/fhirpath.js/blob/master/LICENSE.md
So, I would think any needed changes would be fairly easy.
Paul Lynch (Dec 13 2018 at 21:53):
@Grahame Grieve Another question that came up during discussion here, is whether if we transferred fhirpath.js to FHIR, we would still be permitted to keep our own copy of it under the LHC GitHub page (https://github.com/lhncbc). I think I could set that up to be a fork of the FHIR one, so underneath it would say "Forked from FHIR/fhirpath.js" as GitHub does for forked packages. It is thought to be somewhat desirable to keep a reference there on the LHC page as a listing of our work.
Grahame Grieve (Dec 13 2018 at 21:55):
yes you can always keep a fork
Paul Lynch (Dec 14 2018 at 15:26):
That sounds good. I am looking into getting approval from NLM for transferring it to FHIR; it might take a few days (optimistically) to get an answer.
Last updated: Apr 12 2022 at 19:14 UTC
