You are currently browsing the monthly archive for October 2014.
Over at the Strategizingblog, I have blogged about a current pardigmatic struggle in the realm of organizational strategy research. In a recent article in the Strategic Management Journal, Bromiley and Rau (2014, Preprint-PDF) suggest to adopt a “Practice-based View” (PBV) on strategy. What sounds very similar to approaches labelled strategy-as-a-practice, is actually merely a rhetorical assimilation tactic:
Effectively, all this renders the PBV practice-based in name only. Neither is the PBV rooted in practice theory nor does it propose a methodological approach equipped to empirically capture practices. Rather, the PBV as outlined by Bormiley and Rau treats practices more or less as variables.
Read the full article.
(leonhard)
In the series “algorithm regulation”, we discuss the implications of the growing importance of technological algorithms as a means of regulation in the digital realm.
The most important international copyright treaty, the Berne Convention for the Protection of Literary and Artistic Works, is quite clear with regard to registration requirements for copyright protection in its Article 5 (2)
“The enjoyment and the exercise of these rights shall not be subject to any formality”
In other words, for the 168 countries covered by the Berne Convention, registration provisions are not an option.* In the digital era, this ban is unfortunate for a number of reasons: Read the rest of this entry »
Over at his Open Enterprise Blog, Glyn Moody explains “Why Open Source is Replacing Open Standards” by quoting Linux Foundation’s Executive Director, Jim Zemlin, as follows:
The largest form of collaboration in the tech industry for 20 years was at standards development organisations – IEEE, ISO, W3C, these things – where in order for companies to interoperate, which was a requirement in tech, they would create a specification, and everyone would implement that. The tech sector is moving on to a world where, in the Internet of things [for example], do you want to have a 500-page specification that you hand to a light bulb manufacturer, or do you want source code that you can hand to that manufacturer that enables interoperability? I think that’s a permanent fixture. People have figured out for a particular non-differentiating infrastucture they want to work on that through open source, rather than creating a spec.
For Moody, replacing open standards with an open source approach brings two “huge advantages”, namely that (1) “compatibility is baked in” and that it (2) “not only saves money, it speeds up development and the pace of innovation”. Functionally, as Moody emphasizes, open source software still represents a standard, whose source code “both defines that standard, and does 99% of the work of implementing it.”