Naming the license

[tompollard]

We should consider giving the license a more general name than the "MIMIC License", so that it can be applied to other datasets that we share (e.g. the eICU Collaborative Research Database).

The Creative Commons licences are an example of licenses that have become very widely used and recognised, and which support modifications for attribution, non-commercial, sharealike, etc.

Please suggest names in this thread!

[tompollard]

If we go for a base license with optional restrictions (similar to Creative Commons), what would be included as modifications?

e.g. LCP Health Data License (core) +/-:

• attribution (BY)
• non-commercial (NC)

Anything else? @alistairewj

[alistairewj]

• obsolescence
• specific purpose

On Tue, Dec 13, 2016 at 3:55 PM, Tom Pollard notifications@github.com wrote:

If we go for a base license with optional restrictions (similar to creative commons), what would be included as modifications?

e.g. LCP Health Data License (core) +/-:

• attribution
• non-commercial

Anything else? @alistairewj https://github.com/alistairewj

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/MIT-LCP/mimic-license/issues/6#issuecomment-266859223, or mute the thread https://github.com/notifications/unsubscribe-auth/ABOSdMuxqjDdapv8c-oeyQJZCEBw7VGIks5rHwZSgaJpZM4LLDWw .

[tompollard]

For obsolescence, are you thinking of a clause that states a fixed expiry date (e.g. researchers must stop using the dataset on 12 Dec 2016)? Can you give a couple of examples of specific purposes?

[alistairewj]

Yes exactly that for obsolesence. For specific purpose I think many licenses of data require that you use it for a specific project (e.g. Philips initially gave us data only for the a-line study).