manton
License?
As far as I can tell, there is no license. While this isn't much of a problem, it would be a good idea to ensure the spec is free to use and distribute.
I would recommend CC0 (essentially public domain) for the spec, and CC0 or CC BY (or CC BY-SA) for other content.
@jhabdas Thanks for the link, though most of the licenses (other than public domain) are for code, rather than other content.
We used Creative Commons for RSS 2.0.
http://cyber.harvard.edu/rss/rss.html#licenseAndAuthorship
Dave
On Friday, September 29, 2017, IBPX [email protected] wrote:
@jhabdas https://github.com/jhabdas Thanks for the link, though most of the licenses (other than public domain) are for code, rather than other content.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/brentsimmons/JSONFeed/issues/110#issuecomment-333194982, or mute the thread https://github.com/notifications/unsubscribe-auth/ABm9O8D8PjUWAbCTb6u-sTPccNxd1_y_ks5snS8BgaJpZM4OWDvL .
-- Typed on an iPad with fat fingers.
@scripting hey dave (honor to have you here) have you seen anyone use XSLT 3.0 to transform your userland stuff or the 2.0 spec into a JSON feed or vice versa?
No. But it’s an interesting idea. If possible it kind of proves the futility of inventing a new format. 🤪
On Tuesday, February 26, 2019, Josh Habdas [email protected] wrote:
@scripting https://github.com/scripting hey dave have you seen anyone use XSLT 3.0 to transform your userland stuff or the 2.0 spec into a JSON feed?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/brentsimmons/JSONFeed/issues/110#issuecomment-467368574, or mute the thread https://github.com/notifications/unsubscribe-auth/ABm9O5PW-SZ_vABrab7Ym1xFkUpB5g1cks5vRQEvgaJpZM4OWDvL .
-- Typed on an iPad with fat fingers.
If you want to try it, this is my RSS feed —
http://scripting.com/rss.xml
Or if you prefer JSON syntax —
http://scripting.com/rss.json
On Tuesday, February 26, 2019, Josh Habdas [email protected] wrote:
@scripting https://github.com/scripting hey dave have you seen anyone use XSLT 3.0 to transform your userland stuff or the 2.0 spec into a JSON feed?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/brentsimmons/JSONFeed/issues/110#issuecomment-467368574, or mute the thread https://github.com/notifications/unsubscribe-auth/ABm9O5PW-SZ_vABrab7Ym1xFkUpB5g1cks5vRQEvgaJpZM4OWDvL .
-- Typed on an iPad with fat fingers.
@brentsimmons Any thought on this? It seems impractical/imprudent to implement JSON Feed without it being explicitly licensed.
I've been thinking about this recently. I think we could make it CC0 (public domain), but all the other authors of the spec will need to chime in before we make a change.
This is unusable without a valid license, please pick one of soon as possible.
The intention is that it will be CC0 (public domain, no copyright at all). We just haven't officially updated the documentation yet. JSON Feed is in widespread use already, though, and has been for years at this point. The license just covers the text itself, not what you can do with it.
As the text contains a standard, it cannot be used without a valid license in many jurisdictions.
It's time to pick a license.
we could make it CC0 (public domain), but all the other authors of the spec will need to chime in before we make a change.
Contact them now, before more time passes.
Yes, I contacted the contributors earlier this year. It will be CC0 (public domain), just need to update the actual license and docs.
Closed in https://github.com/manton/JSONFeed/commit/7fed7625c6646942d4a6c9f3cabde75e2092a58c?
