Domain name for public website
rgommers opened this issue · 8 comments
Now that the consortium name is settled, we looked at finding a good domain name for a website for it. It's not completely obvious what the best domain is. We started with python-data-apis.org, and because that's a bit long we also grabbed data-apis.org (which we could use directly, or forward to the python- version).
If anyone sees a problem with that or has a better idea, please comment.
A proposal: what about OpenDataAPI?
A proposal: what about OpenDataAPI?
I personally find it misleading, "open data" means something else to me. Also, the consortium name was already agreed for what I know. This issue is to see if there is a better idea for the domain (or do you mean opendataapi.org?).
A proposal: what about OpenDataAPI?
I personally find it misleading, "open data" means something else to me. Also, the consortium name was already agreed for what I know. This issue is to see if there is a better idea for the domain (or do you mean opendataapi.org?).
Yes, opendataapi.org. @datapythonista Marc, can you, please, elaborate why it is misleading?
I find "open data" a bit misleading, as well, given the term's usage in data transparency initiatives. And atm, the API is not "open" in its standardization, given it's being developed within the consortium. So I find the usage of "open" to be somewhat problematic.
Sure, open data usually refers to data that is freely available. For example, I'd like my government to publish all the data of how they are spending my money, and I would use open data to refer to that.
While I'm surely a big fan of open data, I think it's totally unrelated to what we are doing here. The API's we're discussing here, are expected to be implemented in open source software. But this software will be used to work with private data from companies, as much as with open data. So, using "open data", is to me like using "financial data", or "astronomy data" here. A kind of data that is not related or descriptive with the consortium. So, I think it's misleading into making people think that we have something to do with open data, when there relation is minimal.
I find "open data" a bit misleading, as well, given the term's usage in data transparency initiatives. And atm, the API is not "open" in its standardization, given its being developed within the consortium. So I find the usage of "open" to be somewhat problematic.
I can argue that OpenMP (Open Multi-Processing), OpenCL (Open Computing Language), ODF (Open Document Format) are open standards developed by consortiums. Open usually attributes to the usage, and not to the development process. It can be openly and freely used, but closed for changes from outside of the consortium. But I do get your point.
Sure, open data usually refers to data that is freely available. For example, I'd like my government to publish all the data of how they are spending my money, and I would use open data to refer to that.
While I'm surely a big fan of open data, I think it's totally unrelated to what we are doing here. The API's we're discussing here, are expected to be implemented in open source software.
Thanks, I agree, that it could mislead - but would like to point that e.g. OpenAccess is a well known standard Electronic Design Automation API and DB for chip-design tools developed by Si2 consortium. I don't have any strong attachments to 'Open Data', but would like to somehow emphasize openness in the name.
We went with https://data-apis.org/ a long time ago, so let me close this. Thanks all.