Not Signed-In
Which clippings match 'Open Source Files' keyword pg.1 of 1
15 APRIL 2012

Beta blockers? : proprietary data formats may be legally defensible but open standards can be a better spur for innovation

"Thomson [Thomson Reuters] makes the proprietary bibliography software EndNote, and claims that Zotero is causing its commercial business 'irreparable harm' and is wilfully and intentionally destroying Thomson's customer base. In particular, Thomson is demanding that GMU stop distributing the newer beta–version of Zotero that allegedly allows EndNote's proprietary data format for storing journal citation styles to be converted into an open–standard format readable by Zotero and other software. Thomson claims that Zotero 'reverse engineered or decompiled' not only the format, but also the EndNote software itself. ...

Litigation, which may go to a jury trial, is pending, so judging this case on its legal merits would be premature. But on a more general level, the virtues of interoperability and easy data–sharing among researchers are worth restating. Imagine if Microsoft Word or Excel files could be opened and saved only in these proprietary formats, for example. It would be impossible for OpenOffice and other such software to read and save these files using open standards – as they can legally do.

Competition between open–source and proprietary software is long–running, as personified by the struggle between Windows and Linux for desktop and server operating systems, but also in many branches of software used by scientists. Researchers tend to lean towards open sharing, but they will also pay for added–value features, and it's important that the playing field is level. Ultimately, the customer is king."

(Nature, p.708)

Nature Volume 455, p.708 (9 October 2008) | doi:10.1038/455708a; Published online 8 October 2008, Nature Publishing Group, a division of Macmillan Publishers Limited.



2006 • added-value features • authorshipbibliography softwareCenter for History and New MediacitationcopyrightDan Cohen • data format • digital informationEndNoteGeorge Mason Universityinteroperabilityknowledge integrationlawsuitlevel playing fieldLinuxMicrosoft ExcelMicrosoft WindowsMicrosoft WordNature (journal) • open sharing • open sourceopen source filesopen source software • open standard format • open standards • OpenOffice • operating systemorganise and share • OS • ownershipproprietary • proprietary data formats • proprietary formats • proprietary software • researchersreverse engineering • science news • science policy • Sean Takatssoftwaretechnology • Thomson Reuters • trademark infringment • Zotero


Simon Perkins
17 JUNE 2011

GitHub, Collaboration, and Haters

"You've probably all seen the article on RWW yesterday about GitHub surpassing, GoogleCode, and Codeplex. Kudos to our friends at GitHub! They've had some great ideas and have executed them flawlessly. They have made Git the number one VCS used by software devs. Most importantly, they have helped open source grow, and helped open source projects be more successful, and really that's all we care about. Many people use us together; GitHub for collaboration, and for distribution, since our end–user interface is a little more friendly to the non–techies. Really it just comes down to using whatever tools work best for you and your team, and we totally understand that. So from SF to GitHub– High five! ...

Open source is all about choice, transparency, and collaboration, not hating on others. Use what tools work best for you, and respect that others may choose a different path."

(SourceForge Community Blog)


2011 • Black Duck • CodePlex • constructive feedback • downloadable projects • GitHub • Google Code • haters • hating on us • metricsno single standardopen sourceopen source communityopen source filesopen source platform • open source projects • opinionpopular votepopularity • popularity contest • project-sharing website • ReadWrite (news) • ReadWriteWeb (news) • Redmonk (site) • relevance • RWW • software development • software version control • SourceForgeusage • usage analysis • user preferences • VCS • version control • version control system


Simon Perkins

to Folksonomy

Can't access your account?

New to Folksonomy?

Sign-Up or learn more.