tag:blogger.com,1999:blog-376803705595763527.post1877157028812649990..comments2023-04-13T01:00:50.872-07:00Comments on malat's blog: Private DICOM dictionaryAnonymoushttp://www.blogger.com/profile/14336421488587965756noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-376803705595763527.post-21761598478505915042009-11-19T06:52:18.840-08:002009-11-19T06:52:18.840-08:00The pydicom code always says "based on an MIT...The pydicom code always says "based on an MIT license" and refers to the license.txt file for more details. That file includes mdcm and GDCM licenses with respect to the file used by make_private_dict.py. <br /><br />No files from either project are copied directly by pydicom; the file in question is used as data for a conversion. When I first examined this, I thought that such use did not require extension of LGPL to pydicom, but nevertheless included the reference in the license statement for full disclosure.<br /><br />Unfortunately, google code website does not allow such fine distinctions. I have changed the google code site to LGPL until this can be addressed.<br /><br />You suggestion to use the GDCM XML private dictionary is a good one. I would gladly have used it, but was not aware of it until now.DMasonhttps://www.blogger.com/profile/13210760602104208327noreply@blogger.com