Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Das License? #1

Open
jsonin opened this issue Jan 3, 2019 · 3 comments
Open

Das License? #1

jsonin opened this issue Jan 3, 2019 · 3 comments

Comments

@jsonin
Copy link

jsonin commented Jan 3, 2019

What's the license on this beauty?
Apache, MIT, or... ?

@ftrotter
Copy link
Contributor

ftrotter commented Jan 3, 2019

Well.. This project is something more like a License than it is software that is licensed.

Obviously, using the schema is free and anyone is welcome to use it without cost.

But if it was "open source" then deravites would be acceptable and frankly, the whole point of this is to be a standard that you either adhere to or do not. If people could download the schema, and then remove a field or change the layout of the files... then that ends up making it harder to the end user to work with the data.. and negates the value of the schema.

So my top candidate for the license is creative commons Attribution-NoDerivatives 4.0 International (CC BY-ND 4.0) https://creativecommons.org/licenses/by-nd/4.0/

This would not allow for derivatives but ensure that we had a reliable license that people could trust (i.e. not written by us, just for this purpose)

What do you think?

-FT

@jsonin
Copy link
Author

jsonin commented Jan 4, 2019

Reasonable response.

Does CMS sign off on the schema?
Or is this a different play?

@ftrotter
Copy link
Contributor

ftrotter commented Jan 4, 2019

CMS has decided not to decide. According to their standard, it must be "machine readable". They specifically said that a pdf is not machine readable.

They did not specifically say so, but I think it can be further inferred that the HHS policy would be compliant with Project Open Data which does indicate that the underlying format standard should also be based on open standards.

Which really means that the choice is:

  • XML which no one uses for data anymore, because JSON is better
  • JSON which is a reasonable choice, but more fragile than CSV
  • CSV comma delimited was what we chose for the specification.

-FT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants