No edit summary |
(→Summary of current practices: - clarify page) |
||
| Line 5: | Line 5: | ||
[http://www.opendefinition.org/osd OSD]: Open data (private data only open to the user it's about) and public free software. | [http://www.opendefinition.org/osd OSD]: Open data (private data only open to the user it's about) and public free software. | ||
[http://live.gnome.org/FreeOpenServicesDefinition FOSD]: | [http://live.gnome.org/FreeOpenServicesDefinition FOSD]: this is more of a brainstorming/reference page than a definition; the draft definition produced from that process has been mailed to the mailing list and if someone nags me I'll put it on the web somewhere :) | ||
== Open issues == | == Open issues == | ||
Revision as of 16:23, 12 March 2008
Definitions can be used, as in the Free Software and Free Culture definitions, to highlight network services that meet a standard of freedom.
Summary of current practices
OSD: Open data (private data only open to the user it's about) and public free software.
FOSD: this is more of a brainstorming/reference page than a definition; the draft definition produced from that process has been mailed to the mailing list and if someone nags me I'll put it on the web somewhere :)
Open issues
- What do you do about Googlejuice?
- What do you do about identity?
- Are external dependencies permitted?
- Ease-of-install requirements?
- Interoperability requirements?
- Requirement to share aggregate/anonymized user data?
