Archive for 2014

Keep Fighting Forward

Tuesday, February 11th, 2014

Today is the day to mass call for regulation of mass surveillance. I did, please do it too.

I’m still underwhelmed by the rearguard nature of such actions, wonder how long they continue to be effective (e.g., when co-opted, or when policymakers realize mass calls don’t translate into votes, or forever…since at least 1996), and am even enraged by their focus on symptoms. But my feelings are probably wrong. Part of me applauds those who enjoy fighting the shortest term and broadest appeal possible battles. Such probably helps prevent things from getting worse, at least for a time, and that’s really valuable. Anyone who believes things must get worse before they get better is dangerous, because that’s when real trolls take over, damn your revolution.

I enjoyed Don Marti’s imperfect but perfectly provocative analogy, which I guess implies (he doesn’t say) the correct response to mass surveillance is to spend on end-to-end crypto, rejection of private tracking, decentralization, and other countermeasures, sealing net communications from security state poison. I’m all for that, and wish advocacy for same were a big part of mass calls to action like today’s. But I see the two as mostly complementary, as much as I’d like to scream “you’re doing it entirely wrong!”

Also QuestionCopyright’s assertion that Copyright + Internet = Surveillance. Or another version: Internet, Privacy, Copyright; Choose Two. I could quibble that these are too weak (freedom was infringed by copyright before the net) and too strong (not binary), but helpfully provocative.

Addendum: Also, Renata Avila:

For me is . Otherwise, we will be in serious trouble. Donate to resistance tools like or

Art of cc-community

Sunday, February 9th, 2014

The reading group (curated by Nate Aune) I mentioned as having started with Coase’s Penguin is on to its first book: The Art of Community: Building the New Age of Participation, 2nd Edition (2012) by Jono Bacon. It happens this corresponds with another delayed book review, though only by 18 months in this case, and largely motivated by the book including an interview with me (reproduced below).

This is a large tome. You can download it as a 20 megabyte PDF with 574 pages (linked from the book website along with usual purchase locations). I see substantial portions of about 5 books therein:

  • Autobiography of Jono Bacon. Less of this book is latent in the tome than those below, but tales of Bacon’s life are interspersed, and his personality comes through strong (n.b. Bacon uses “tales” to denote stories told within a community, not “tall tales”; similarly “fables” to denote stories that explain a community, not myths).
  • Inside the Ubuntu/Canonical Ltd. community: how it works, its tales and fables.
  • Tools and practices for managing an open source software community, especially one led by a for-profit company (corresponding to Ubuntu/Canonical Ltd. above).
  • Reference/workbook for community managers and their managers. Also interspersed throughout, but especially the chapter on hiring a community manager.
  • Community management casebook, heavily leaning on interviews with open source software project managers, but also many other types of community leaders and managers.

If any one of these piques your interest, it’s worth downloading the PDF and clicking in the ToC or word-searching, as is your style. If multiple seem compelling (say your company wants to hire a community manager, or you want to be hired as a community manager by a company), then reading the whole thing carefully would be a good use of your time.

(Of course it shouldn’t be your only reading, not least because “community management” is fraught, maybe especially in service of a for profit, and there exist plenty of criticisms of the Ubuntu/Canonical Ltd. community. I even agree with some of those criticisms, but my top level “complaint” about Ubuntu/Canonical Ltd. is that they haven’t been as successful in the marketplace as I’d like, i.e., they haven’t supplanted Microsoft! ☻ Bacon and company continue to work on that from a community angle.)

Interview

The interview with me in the book (numbered pages 492-495), conducted late 2011. The “cc-community” in the title of this post refers to a mailing list not mentioned in the interview.

You have been at the CC for a long time now. How did the organization look when you joined?

I joined CC in April, 2003, a few months after the first CC licenses were released. We were in the basement of the Stanford Law School, as that’s where Lawrence Lessig was. Various people had been involved over the preceding year, but essentially there were three staff just before I joined. There was a very loose community initially, based on the notoriety of Lessig and other founders and some friendly coverage in the usual (for the time) geek outlets such as Slashdot — more a variety of well-wishers than a community.

What kind of community did you set out to grow?

The other person CC hired in April, 2003 was our first international coordinator, based in Berlin. One community that we set out to grow, initially via this position, was a network of legal scholars around the world, who could collectively figure out how CC licenses work with copyright law in various jurisdictions around the world. This is the main community that CC was and is intentional about growing. We also set out to grow connections with related communities, eg open access, open education, open source, and mostly deliberately stayed away from trying to create “CC” subcommunities within these movements, and instead play a supporting role.

There always has been a mostly latent “CC community” of people who aren’t tied to a CC affiliate institution, and may or may not be involved with other nearby movements, but for whatever reason see CC as one of their primary passions — which is fantastic of course. CC the organization hasn’t ever really set out to “organize” this largely latent community, mostly due to lack of bandwidth (admittedly this could seem short sighted) and it isn’t clear how this community ought be cultivated — it is a very diverse set of people. I and some others see mobilizing this community (I’m actually more comfortable thinking about it as a movement) in some form as one of the biggest opportunities CC has in its next decade.

What approaches did you use to grow your community?

Regarding the international community of legal scholars we intentionally created, we gave them interesting, challenging, but highly delimited work — “porting” the CC license suite to their respective jurisdictions. (A “port” is usually both a linguistic translation and legal “translation” to reference local laws, drafting style, etc, where appropriate to hopefully make the ported licenses more understandable to the legal community in a given jurisdiction, but achieve the same affects to the extent possible.) This element of work made it relatively easy to determine what kind of team (usually composed of people from one or more local institutions) could be part of the formal community — they had to bring certain legal expertise, interest, and capacity — and gave community members a strong sense of ownership and contribution.

In the past 8 years CC licenses have been ported to over 50 jurisdictions via this process and community. In a sense this is just another instance of work occurring in chunks amenable to work being done by lots of different people, but I think the subject matter and large size and duration of the chunks makes it fairly interesting. Although many of the affiliate projects have formed their own local communities that have given feedback on license drafts, the overall process is highly controlled by experts, and openness to attracting and up-leveling drive-by contributors not much of a factor. This arrangement has been shown to not be competitive for building an encyclopedia, nor for most software and cultural projects, but perhaps should be evaluated if one thinks their project requires long-term commitment from a community with narrow and rare expertise.

Among the community involved in license porting, there has always been desire to also do advocacy and outreach, and sometimes art projects and software development. This has occurred organically, but over the last year or so we’ve also formally recognized those activities as potential responsibilities of a CC affiliate. While producing interesting work, a community that only really needs a few lawyers in each country is self-limiting. The aforementioned activities need unlimited resources, including the involvement of many more lawyers, who are crucial in persuading institutions and governments to adopt CC tools as policy, for example. Probably over the next few years there will be many more institutions and people officially involved in the CC community, with impressive outreach and projects around the world as a result.

The CC philosophy, particularly a few years ago, was fairly alien to the normal culture of content licensing and distribution practised by large record labels and studios. How did you communicate this message to your community?

Building a commons is still completely alien to “big content”; not even relevant really. Giving up the ability to legally persecute fans and users is a bridge too far for those whose dominant interest is protecting and milking existing revenue streams for however many quarters their horizon is. If it takes destroying the Internet to do that, so be it. This has to change, but the change won’t come from big content adopting CC licenses wholesale (though of course we appreciate when a progressive element does so for a project, and I’d be happy to be wrong), but through policy change that removes their ability to persecute fans. Have we reached “peak copyright” yet?

Communicating this to the CC community is not a challenge — they already knew how poorly aligned the interest and practice of big content and society are, and for many people this was a motivating factor for getting involved in CC.

The challenge has been figuring out where the commons can make a big difference, given the indifference-to-hostility of big content. The answer has arrived at fairly organically, learning both from the broader community (e.g., FLOSS, Wikipedians, the Open Access movement) and from the CC affiliate community’s work on institutional and government policy. The summary is that CC’s sweet spots are community and mass collaboration projects, where legal freedoms are necessary for a project to scale, just like in FLOSS, and in publicly interested policy, where the policymaker might be a funder, and institution, or a government. In both of these cases, the appropriate CC license or public domain tool is a standard, well understood and recognized instrument that can be made the legal basis of a project, or slotted into a broader policy intended to benefit the public, instead of engaging in expensive debate and reinvention — and there’s a big community of experts eager to help, wherever one is in the world.

There is a passionate CC community out there. How did you build a community that takes the CC ethos and spreads it further and advocating it to others?

Sharing, giving credit where due, valuing the common good, using technology to encourage such, not persecuting people who do those very natural things — things that one might recognized as “the CC ethos” — all precede CC. They’re essentially human. CC created some practical tools that one can use to further those ends and a brand that denotes such an ethos at our particular juncture in history. People would’ve been spreading that ethos in the same contexts CC is now — one can see an explosion of experiments in open content licensing in the years just before CC launched. Hopefully overall CC has made those people more effective than they would’ve been without a fairly high profile and well resourced (but tiny in the scheme of things) license steward, i.e., CC.

We did make an attempt approximately 2005-2008 to provide a nexus for open movements to meet and collaborate, a subsidiary called iCommons (now a small independent charity) that ran a series of “iSummits”. These turned out to be mostly useful for bringing the CC community together, so our next global gathering, which did not occur until September, 2011, made no pretense of being anything other than a CC summit. There remains huge opportunity to at appropriate times work together with other communities and movements with an overlapping ethos — more of that is happening, but slowly, and not under an umbrella brand.

CC is a now well established organization and community. How do you keep your community passionate about the CC and Free Culture?

Regarding the CC affiliate community (copyright and other experts mentioned above), carefully and collaboratively. Some of the core work by that community is changing — we’re working on version 4.0 of the CC license suite now, which has the aim of being unambiguously global — porting as it has been done so far may end, or at least will be a special case. We have to move and diversity the work of this community, and it has to be even more vital and challenging work, e.g. CC adoption as policy, leveraging CC’s reputation in nearby policy debates impactful to the commons, CC as a subject of legal, economic, and other research, and interfacing with WIPO and other international institutions. We have to strive to make CC a truly international organization itself. What this means for governance, staffing, fundraising, the structure of relationships with affiliates and other organizations — we don’t know yet, and will probably always be evolving.

Regarding the broader community and potential movement, the flip answer is that we don’t have to do anything. The passion is there, and free culture, open access, open education, etc, provide endless good news and opportunity for all interested — and occasionally we get a gift in the form of a ridiculously incorrect attack on CC from a big content executive — that fires everyone up. However, there’s a lot that we do, the single most important one being serving as a great license steward, which includes everything from explaining and answering questions to advocacy to actually getting the licenses “right” so that they’re the best tools for growing the commons. If our explanations of the licenses are confusing, or we have licenses that don’t serve to build the commons, it puts a real damper on the ability of the community to advocate and spread CC, and their passion for doing so.

The 4.0 process is also going to be crucial for engaging the broader community, and be a determinant of how much passion and energy we see from them over the next decade. My highest aspiration would be for the 4.0 licenses to have received overwhelming input and buy-in from both the broadest set of “netizens” (if I may use a 1990s term) interested in the common good and policymakers, forming a standard for info- and innovation-policy and norms for a generation. Coming anywhere near that goal will require lots of community organizing!

CC is a funded by donations. What approaches have you used to gather these donations?

So far the vast majority of our funding has come from U.S.-based private foundations. Our main effort for community support (which I consider the most healthy form of funding, and should over time become the most important pillar) has consisted of an annual fall campaign, mostly conducted online — think a micro version of the Wikimedia fundraising campaigns that most readers should have seen. CC has a lot of learning and growth to do here. The main reason to cultivate the CC community is that doing will be instrumental for accomplishing our mission — but it is true that we hope that a portion of the community has the means and feels our work is important enough to donate each year.

If you enjoyed that, check out the other community case book interviews: Linus Torvalds, Linux; Mike Shinoda, Linkin Park; Mårten Mickos, MySQL and Eucalyptus; Tim O’Reilly, O’Reilly Media; Carolyn Mellor, X.commerce, PayPal, and eBay; Ilan Rabinovitch, Southern California Linux Expo; Richard Esguerra, Humble Indie Bundle; Mark Bussler, Classic Game Room; Mary Colvig, Mozilla; Dries Buytaert, Drupal and Acquia; and James Spafford, Media Molecule.

If you enjoyed the book, Bacon also runs community leadership conferences.

Sleepwalking past Freedom’s Commons, or how peer production could increase democracy, equality, freedom, and innovation, all of them!

Sunday, February 9th, 2014

2007:

The most interesting parts of ‘s The Wealth of Networks concern how peer production facilitates liberal values. I’ll blog a review in the fullness of time.

In lieu of that which may never come, some motivated notes on Coase’s Penguin, or Linux and the Nature of the Firm (2002, 78 pages) and Freedom in the Commons: Towards a Political Economy of Information (2003, 32 pages; based on a 2002 lecture). A friend wanted to trial a book group with the former. Re-reading that led me to the latter, which I hadn’t read before. Reading them together, or even just the latter, might be a good alternative to reading The Wealth of Networks: How Social Production Transforms Markets and Freedom (2006, 473 pages).

As might be expected from decade plus old internet research, some of the examples in the papers and book are a bit stale, but sadly their fundamental challenge remains largely unacknowledged, and only taken as a byproduct. I would love to be convinced otherwise. Is the challenge (or my extrapolation) wrong, unimportant, or being met satisfactorily?

Excerpts from Freedom in the Commons (emphasis added by me in all quotes that follow):

[Commons-based peer production] opens a range of new opportunities for pursuing core political values of liberal societies—democracy, individual freedom, and social justice. These values provide three vectors of political morality along which the shape and dimensions of any liberal society can be plotted. Because, however, they are often contradictory rather than complementary, the pursuit of each of these values places certain limits on how we conceive of and pursue the others, leading different liberal societies to respect them in different patterns.

An underlying efficient limit on how we can pursue any mix of arrangements to implement our commitments to democracy, autonomy, and equality, however, has been the pursuit of productivity and growth.

[Commons-based peer production] can move the boundaries of liberty along all three vectors of liberal political morality.

There is no benevolent historical force, however, that will inexorably lead the technological-economic moment to develop towards an open, diverse, liberal equilibrium. If the transformation occurs, it will lead to substantial redistribution of power and money from the twentieth-century, industrial producers of information, culture, and communications—like Hollywood, the recording industry, and the telecommunications giants—to a widely diffuse population around the globe. None of the industrial giants of yore are going to take this redistribution lying down. Technology will not overcome their resistance through some insurmountable progressive impulse. The reorganization of production, and the advances it can bring in democracy, autonomy, and social justice will emerge, if it emerges, only as a result of social and political action. To make it possible, it is crucial that we develop an understanding of what is at stake and what are the possible avenues for social and political action. But I have no illusions, and offer no reassurances, that any of this will in fact come to pass. I can only say that without an effort to focus our attention on what matters, the smoke and mirrors of flashy toys and more convenient shopping will be as enlightening as Aldous Huxley’s soma and feelies, and as socially constructive as his orgy porgy.

Let us think, then, of our being thrust into this moment as a challenge. We are in the midst of a technological, economic, and organizational transformation that allows us to renegotiate the terms of freedom, justice, and productivity in the information society. How we shall live in this new environment will largely depend on policy choices that we will make over the next decade or two. To be able to understand these choices, to be able to make them well, we must understand that they are part of a social and political choice—a choice about how to be free, equal, and productive human beings under anew set of technological and economic conditions. As economic policy, letting yesterday’s winners dictate the terms of economic competition tomorrow is disastrous. As social policy, missing an opportunity to enrich democracy, freedom, and equality in our society, while maintaining or even enhancing our productivity, is unforgivable.

Although the claim that the Internet leads to some form or another of “decentralization” is not new, the fundamental role played in this transformation by the emergence of non-market, nonproprietary production and distribution is often over-looked, if not willfully ignored.

First, if the networked information economy is permitted to emerge from the institutional battle, it will enable an outward shift of the limits that productivity places on the political imagination. Second, a society committed to any positive combination of the three values needs to adopt robust policies to facilitate these modes of production,because facilitating these modes of production does not represent a choice between productivity and liberal values, but rather an opportunity actually to relax the efficient limit on the plausible set of political arrangements available given the constraints of productivity.

We are at a moment in our history at which the terms of freedom and justice are up for grabs. We have an opportunity to improve the way we govern ourselves—both as members of communities and as autonomous individuals. We have an opportunity to be more just at the very core of our economic system. The practical steps we must take to reshape the boundaries of the possible in political morality and to improve the pattern of liberal society will likely improve productivity and growth through greater innovation and creativity. Instead of seizing these opportunities, however, we are sleepwalking.

What arrangements favor reorganization towards commons-based peer production? From Coase’s Penguin:

This suggests that peer production will thrive where projects have three characteristics. First, they must be modular. That is, they must be divisible into components, or modules, each of which can be produced of the production of the others. This enables production to be incremental and asynchronous, pooling the efforts of different people, with different capabilities, who are available at different times. Second, the granularity of the modules is important and refers to the sizes of the project’s modules. For a peer production process to pool successfully a relatively large number of contributors, the modules should be predominately fine-grained, or small in size. This allows the project to capture contributions from large numbers of contributors whose motivation levels will not sustain anything more than small efforts toward the project. Novels, for example, at least those that look like our current conception of a novel, are likely to prove resistant to peer production. In addition, a project will likely be more efficient if it can accommodate variously sized contributions. Heterogeneous granularity will allow people with different levels of motivation to collaborate by making smaller- or larger-grained contributions, consistent with their levels of motivation. Third, and finally, a successful peer production enterprise must have low-cost integration, which includes both quality control over the modules and a mechanism for integrating the contributions into the finished product.

Regulators concerned with fostering innovation may better direct their efforts toward providing the institutional tools that would help thousands of people to collaborate without appropriating their joint product, making the information they produce freely available rather than spending their efforts to increase the scope and sophistication of the mechanisms for private appropriation of this public good as they now do.

That we cannot fully understand a phenomenon does not mean that it does not exist. That a seemingly growing phenomenon refuses to fit our longstanding perceptions of how people behave and how economic growth occurs counsels closer attention, not studied indifference and ignorance.  Commons-based peer production presents a fascinating phenomenon that could allow us to tap substantially underutilized reserves of human creative effort. It is of central importance that we not squelch peer production, but that we create the institutional conditions needed for it to flourish.

There’s been some progress on institutional tools (i.e., policy arrangements writ large, the result of “political action” above) in the 11 or so years since (e.g., Open Access mandates), but not nearly enough to outweigh global ratcheting of intellectual freedom infringing regimes, despite the occasional success of rearguard actions against such ratcheting. Neither these rearguard actions, nor mainstream (nor reformist) discussion of “reform” put commons at the center of their concerns. The best we can expect from this sleepwalking is to muddle through, with policy protecting and promoting commons where such is coincidentally aligned with some industrial interest (often simplified to “Google” in the past several years, but that won’t last forever).

My extrapolation (again, tell me if facile or wrong): shifting production arrangements so as to favor commons-based peer production is as important as, complementary to, and almost necessary for positive policy change. Commons-based product competition simultaneously changes the facts on the ground, the range of policies imaginable, and potentially create a commons “industrial” interest group which is recognizably important to regulators and makes commons-based peer production favoring policy central to its demands — the likely Wikimedia response to the European Commission copyright consultation is a hopeful example.

There has been lots of progress on improving commons-based peer production (e.g., some trends), but also not nearly enough to keep up with proprietary innovation, particularly lacking and missing huge opportunities where proprietary incumbents real advantages sit — not production per se, but funding and distribution/marketing/cultural relevance making. Improving commons-based peer production, shifting the commanding heights (i.e., Hollywood premium video and massively expensive and captured pharma regulatory apparatus) to forms more amenable to commons-based peer production, and expanding the scope of commons-based peer production to include funding and relevance making are among the most potent political projects of our time.

Wake up. ^_^

RDFa initial context & one dc:

Tuesday, February 4th, 2014

One of the nice things to come out of RDFa 1.1 is its initial context — a list of vocabularies with prefixes which may be used without having to define locally. In other words, just write, e.g., property="dc:title" without having to first write prefix="dc: http://purl.org/dc/terms/".

In addition to making RDFa a lot less painful to use, the list is a good starting place for figuring out what vocabularies to use (if you must), perhaps even for non-RDFa applications — the list is machine-readable of course; I was reminded to write this post when giving feedback on a friend’s proposal to use prefix:property headers in a CSV file for a custom application, and by a recent announcement of the addition of three new predefined prefixes.

Survey data such as Linked Open Vocabularies can also help figure out what to use. Unfortunately LOV and the RDFa 1.1 initial context don’t agree 100% on prefix naming, and neither provides much in the way of guidance. I think there’s room for a highly opinionated and regularly updated guide to what vocabularies to use. I’m no expert, it probably already exists — please inform me!

dc:

The first thing I’d put in such an opinionated guide is to start one’s vocabulary search with Dublin Core. Trivial, right? But there is an under-documented subtlety which I find myself pointing out when a friend runs something like the aforementioned by me — DC means DC Terms. While it’s obvious that DC Terms is a superset of DC Elements, it’s harder to find evidence that using the former is best practice for new applications, and that the latter is not still the canonical vocabulary to start with. What I’ve gathered on this follows. I realize that the URIs for individual properties and classes, the prefixes used to abbreviate those URIs, and the documents which define (in English and RDF) properties and classes are distinct but interdependent. Prefixes are surely the most trivial and uninteresting, but for most people I imagine they’re important signals and documentation, thus I go on about them…

Namespace Policy for the Dublin Core Metadata Initiative (DCMI) (emphasis added):

The DCMI namespace URI for the collection of legacy properties that make up the Dublin Core Metadata Element Set, Version 1.1 [DCMES] is: http://purl.org/dc/elements/1.1/

Dublin Core Metadata Element Set, Version 1.1 (emphasis added):

Since 1998, when these fifteen elements entered into a standardization track, notions of best practice in the Semantic Web have evolved to include the assignment of formal domains and ranges in addition to definitions in natural language. Domains and ranges specify what kind of described resources and value resources are associated with a given property. Domains and ranges express the meanings implicit in natural-language definitions in an explicit form that is usable for the automatic processing of logical inferences. When a given property is encountered, an inferencing application may use information about the domains and ranges assigned to a property in order to make inferences about the resources described thereby.

Since January 2008, therefore, DCMI includes formal domains and ranges in the definitions of its properties. So as not to affect the conformance of existing implementations of “simple Dublin Core” in RDF, domains and ranges have not been specified for the fifteen properties of the dc: namespace (http://purl.org/dc/elements/1.1/). Rather, fifteen new properties with “names” identical to those of the Dublin Core Metadata Element Set Version 1.1 have been created in the dcterms: namespace (http://purl.org/dc/terms/). These fifteen new properties have been defined as subproperties of the corresponding properties of DCMES Version 1.1 and assigned domains and ranges as specified in the more comprehensive document “DCMI Metadata Terms” [DCTERMS].

Implementers may freely choose to use these fifteen properties either in their legacy dc: variant (e.g., http://purl.org/dc/elements/1.1/creator) or in the dcterms: variant (e.g., http://purl.org/dc/terms/creator) depending on application requirements. The RDF schemas of the DCMI namespaces describe the subproperty relation of dcterms:creator to dc:creator for use by Semantic Web-aware applications. Over time, however, implementers are encouraged to use the semantically more precise dcterms: properties, as they more fully follow emerging notions of best practice for machine-processable metadata.

The first two paragraphs explain why a new vocabulary was minted (so that the more precise definitions of properties already in DC Elements do not change the behavior of existing implementations; had only new terms and classes been added, maybe they could have been added to the DC Elements vocabulary, but maybe this is ahistoric, as many of the additional “qualified” DC Terms existed since 2000). The third paragraph explains that DC Terms should be used for new applications. Unfortunately the text informally (the prefixes aren’t used anywhere) notes the prefixes dc: and dcterms:, which I’ve found is not helpful in getting people to focus only on DC Terms.

Expressing Dublin Core metadata using the Resource Description Framework also notes the dc: and dcterms: prefixes for use in the document’s examples (which don’t ever actually use dc:).

Some of these documents have been updated slightly, but I believe their current versions are little changed from about 2008, a year after the proposal of the DC Terms refinements.

How to use DCMI Metadata as linked data uses the dc: and dcterms: prefixes and is clear about the ranges of properties of each: there is no incorrect usage of, e.g., purl.org/dc/elements/1.1/creator because it has no defined range nor domain, while purl.org/dc/terms/creator must be a non-literal, a purl.org/dc/terms/Agent. Perhaps this makes DC Terms seem scarier and partially explains the persistence of DC Elements. More likely I’d guess few know about the difference and lots of use of the DC Terms with non-literal ranges are used with literals in the wild (I might be guilty on occasion).

FAQ/DC and DCTERMS Namespaces:

It is not incorrect to continue using dc:subject and dc:title — alot of Semantic Web data still does — and since the range of those properties is unspecified, it is not actually incorrect to use (for example) dc:subject with a literal value or dc:title with a non-literal value. However, good Semantic Web practice is to use properties consistently in accordance with formal ranges, so implementers are encouraged to use the more precisely defined dcterms: properties.
Update, December 2011: It is worth noting that the Schema.org initiative is taking a pragmatic approach towards the formal ranges of their properties:

We also expect that often, where we expect a property value of type Person, Place, Organization or some other subClassOf Thing, we will get a text string. In the spirit of “some data is better than none”, we will accept this markup and do the best we can.

What constitutes “best practice” in this area is bound to evolve with implementation experience over time.

There you have people supplying literals for properties expecting non-literals. Schema.org RDF mappings do not formally condone this pragmatic approach, otherwise you’d see the likes of (addition in bold):

schema:creator a rdf:Property;
    rdfs:label "Creator"@en;
    rdfs:comment "The creator/author of this CreativeWork or UserComments. This is the same as the Author property for CreativeWork."@en;
    rdfs:domain [ a owl:Class; owl:unionOf (schema:UserComments schema:CreativeWork) ];
    rdfs:range [ a owl:Class; owl:unionOf (schema:Organization schema:Person xsd:string) ];
    rdfs:isDefinedBy ;
    rdfs:isDefinedBy ;

Also from 2011, a discussion of what prefixes to use in the RDFa initial context. Decision (Ivan Herman):

For the records: after having also discussed on yesterday’s telecom, I have made the changes on the profile files yesterday evening. The prefix set in the profile for http://purl.org/dc/terms/ is set to ‘dc’.

Read the expert input of Dan Brickley, Mikael Nilsson, and Thomas Baker. The initial context defines both dc: and dcterms: as prefixes for DC Terms, relegating DC Elements to dc11::

dc http://purl.org/dc/terms/ Dublin Core Metadata Terms DCMI Metadata Terms
dcterms http://purl.org/dc/terms/ Dublin Core Metadata Terms DCMI Metadata Terms
dc11 http://purl.org/dc/elements/1.1/ Dublin Core Metadata Element Set, Version 1.1 Dublin Core Metadata Element Set, Version 1.1

I found the above discussion on LOV’s entries for DC Terms and DC Elements, which use dcterms: and dce: prefixes respectively:

(2013-03-07) Bernard Vatant: Prefix restored to dcterms

(2013-06-17) Bernard Vatant: Although “dc” is often used as the prefix for this vocabulary, it’s also sometimes used for DC terms, so we preferred to use the less ambiguous “dce” and “dcterms” in LOV. See usage at http://prefix.cc/dc, http://prefix.cc/dce, http://prefix.cc/dcterms, and more discussion at http://bit.ly/uPuUTT.

I think the discussion instead supports using dc: and dc11: (because that’s what the RDFa initial context uses) instead. LOV doesn’t have a public source repository or issue tracker currently, but I understand it eventually will.

Now I have this grab-bag blog post to send to friends who propose using DC Elements. Please correct me if I’m wrong, and especially if a more concise (on this topic) and credible document exists, so I can send that instead; perhaps something like an opinionated guide to metadata mentioned way above.

Another topic such a guide might cover, perhaps as a coda, would be what to do if you really need to develop a new vocabulary. One thing is you really need to ask for help. The W3C now provides some infrastructure for doing this. Or, some qualified dissent from a hugely entertaining blogger called Brinxmat.

Some readers of my blog who have bizarrely read through this post, or skipped to the end, might enjoy Brinxmat’s Attribution licences for data and why you shouldn’t use them (another future issue report for LOV, which uses CC-BY?); I wrote a couple posts in the same blogversation; also a relevant upgrade exhortation.

Technology and wealth Inequality Promotion

Thursday, January 30th, 2014

Sam Altman, Technology and wealth inequality:

Without intervention, technology will probably lead to an untenable disparity—so we probably need some amount of intervention. Technology also increases the total wealth in a way that mostly benefits everyone, but at some point the disparity just feels so unfair it doesn’t matter.

This widening wealth divide is happening at all levels—people, companies, and countries. And either it will keep going, or innovation will stop.

The very first intervention ought be in our innovation policy, which presently is tuned to maximize concentration of wealth and minimize the access of everyone to the benefits of innovation — because our innovation policy is a property/rent seeking regime. A few data points.

Such an intervention won’t stop innovation, but might change it, and we should want that. Beautiful progress is that which is produced by a freedom and equality respecting regime. We ought be suspicious and ashamed of progress which depends on infringing freedom and promoting inequality. If mass spectacle ends when the regime falls, all the better. We’ll love whatever culture we have and create, will be amazed by its innovation, in part encouraged through non-enclosing innovation policy.

If innovation-driven inequality is a big problem, we ought be more highly valuing (including figuring out how to characterize that value) and promoting existing systems which depend on and promote freedom and equality, i.e., commons-based ones such as free/open source software and the Wikimedia movement (and recursively working on equality and diversity within those systems).

Innovation could tend to increase inequality independent of wealth concentrating, property/rent-seeking based innovation policies and other political factors. If this is the case (or honestly even if it is not), I’m always disappointed that progressivity of tax systems isn’t central to the debate — and I don’t mean marginal income tax rates. Basically property > income > sales. Further, property property can’t be moved and taxing it doesn’t require extensive privacy invasions. In theory I’d expect the strongest states and most free and equal societies of the future to strongly prefer real property taxation over other systems. But perhaps path dependencies and other factors will swamp this (and innovation policy as well).

Public domain wins copyright week!

Sunday, January 19th, 2014

public domain wins copyright weekEFF coordinated a six day copyright week, with suggested readings and actions in support of six principles, below with readings + actions count:

  • Transparency: 10 + 1 = 11
  • Building and Defending a Robust Public Domain: 16 + 0 = 16
  • Open Access: 9 + 2 = 11
  • You Bought it, You Own It: 8 + 3 = 11
  • Fair Use Rights: 14 + 1 = 15
  • Getting Copyright Right: 7 + 1 = 8

I couldn’t help but notice that the public domain “wins” by the metric of total readings + actions, perhaps indicative of relative enthusiasm and evaluation of importance by the communities EFF reaches. Good.

The apparent “loser” is getting copyright right, which I’ll also take undue satisfaction in: it’s an impoverished objective, relative to expanding and protecting intellectual freedom. Alternatively, public domain maximalism (second alternative, corresponding to the runner-up: fair use maximalism) is getting copyright right. But I acknowledge advocating “getting copyright right” (and the entire exercise of copyright week) is a fine thing to do given constraints, and its “loss” is likely due to being a more difficult writing assignment, and falling on the last day.

The latent “loser” though is the role of commons initiatives in changing the knowledge economy, thus the range of policies which can be imagined, and the resources available to support various policies. Some initiatives are mentioned, but almost exclusively as victims of costs imposed by bad policy. Daniel Mietchen’s Wikimedia and Open Access might be the reading closest to what I’d like to see a whole day dedicated to (on the seventh day of copyright week, commoners made their own freedom). Though starting with copyright-imposed costs to the project, Mietchen proceeds to describe collaboration among Wikimedians and the Open Access movement, and ends with (implied) competition:

wider exposure of Open Access materials through Wikimedia platforms may perhaps serve as an incentive for researchers to reconsider whether putting their articles behind access and reuse barriers is an appropriate approach to publishing them.

Related, because it is the domain of the most robust commons initiatives, it is too bad software was not the primary topic of several copyright week readings and actions. But even ignoring the seventh day angle, it is incredibly short-sighted to treat software as a separate category, whether for purposes of study or policy (e.g., copyright). All of the traditional subjects of copyright are now largely made with and mediated by software, but that’s just the beginning. Soon enough, they’ll all be software, or be obsolete. (In hindsight I should have noticed copyright week approaching, and urged various free/open source software initiatives to participate, and explain their policy relevance and potency.)

Back to cheering, I highly recommend at least skimming a few of the readings in each category, linked on the EFF copyright week page. Unless you follow knowledge policy writ large really closely, you’re almost certain to learn something new about policy battles that will play a large role in shaping the future of society.

To make up for the lack of copyright week “actions” recommended for building and defending a robust public domain: sign the public domain manifesto, upgrade your work to the public domain, and enjoy and share the greatest public domain film to date.

Annual thematic doubt

Friday, January 10th, 2014

As promised, my first annual thematic doubt post, expressing doubts I have about themes I blogged about during 2013.

Intellectual Freedom

If this blog were to have a main purpose other than serving as a despository for my tangents, it’d be protecting and promoting intellectual freedom, in particular through the mechanisms of free/open/knowledge commons movements, and in reframing information and innovation policy with freedom and equality outcomes as top. Some representative posts: Economics and the Commons Conference [knowledge stream] report, Flow ∨ incentive 2013 anthology winner, z3R01P. I’m also fond of pointing out where these issues surface in unusual places and surfacing them where they are latent.

I’m fairly convinced on this theme: regimes infringing on intellectual freedom are individual and collective mind-rot, and “merely” accentuate the tendencies toward inequality and control of whatever systems they are embedded in. Mitigating, militating against, outcompeting, and abolishing such regimes are trivially for the good, low risk, and non-revolutionary. But sure, I have doubts:

  • Though I see their accentuation of inequality and control as increasingly important, and high leverage for determining future outcomes, copyright and patent could instead be froth. The cause of intellectual freedom might be better helped by fighting for traditional free speech issues, for tolerance, against mass incarceration, against the drug war, against war, against corruption, for whatever one’s favored economic system is…
  • The voluntarily constructed commons that I emphasize (e.g., free software, open access) could be a trap: everything seems to grow fast as population (and faster, internet population) grows, but this could cloud these commons being systematically outcompeted. Rather than being undersold, product competition from the commons will never outgrow their dwarfish forms, will never shift nor take the commanding heights (e.g., premium video, pharma) and hence are a burden to both policy and beating-of-the-bounds competition. Plus, copyright and the like are mind-rot: generations of commons activists minds have been rotted and co-opted by learning to work within protectionist regimes rather than fighting and ignoring them.
  • An intellectual freedom infringing regime which produced faster technical innovation than an intellectual freedom respecting regime could render the latter irrelevant, like industrial societies rendered agricultural societies irrelevant, and agricultural societies rendered hunter-gatherer societies irrelevant, whatever the effects of those transitions on freedom and other values were. I don’t believe the current regime is anywhere close to being such a thing, nor are the usual “IP maximalism” reforms taking it in that direction. But it is possible that innovation policy is all that matters. Neither freedom and equality nor the rents of incumbents matter, except as obstacles and diversions from discovering and implementing innovation policy optimized to produce the most technical innovation.

I’m not, but can easily imagine being won over by these doubts. Each merits engagement, which could result in much stronger arguments for intellectual freedom, especially knowledge commons.

Critical Cheering

Unplanned, unnoticed by me until late in the year, my most pervasive subtheme was criticism-embedded-in-praise of free/open/commons entities and actions. Representative posts, title replaced with main target: Creative Commons, crowdfunding, Defensive Patent License, Document Freedom Day, DRM-in-HTML5 outrage, EFF, federated social web, Internet Archive, Open Knowledge Foundation, SOPA/ACTA online protests, surveillance outrage, and the Wikimedia movement.

This is an old theme: examples from 2004, 2005, 2006, 2007, 2008, 2011, and 2012. 2009 and 2010 are absent, but the reason for my light blogging here bears some relation to the theme: those are the years I was, in theory, most intensely trying to “walk my talk” at Creative Commons (and mostly failed, side-tracked by trying to get the organization to follow much more basic best practices, and by vast amounts of silliness).

Doubts about the cheering part are implied in the previous section. I’ll focus on the criticism here, but cheering is the larger component, and real: of entities criticized in the above links, in 2013 I donated money to at least EFF, FSF, and Internet Archive, and uncritically promoted all of them at various points. The criticism part amounts to:

  • Gains could be had from better coordination among entities and across domains, ranging from collaboration toward a short term goal (e.g., free format adoption) to diffuse mutual reinforcement that comes from shared knowledge, appreciation, and adoption of free/open/commons tools and materials across domains (e.g., open education people use open source software as inherent part of their practice of openness, and vice versa).
  • The commons are politically potent, in at least two ways: minimally, as existence proof for creativity and innovation in an intellectual freedom respecting regime (carved out); and vastly underappreciated, as destroyer of rents dependent on the intellectual freedom infringing regime, and of resources available for defending those rents and the regime. Commons are not merely to be protected from further bad policy, but are actors in creating a good policy environment, and should be promoted at every turn.

To be clear, my criticism is not usually a call for more “radical” or “extreme” steps or messages, rather more fulsome and coordinated ones. Admittedly, sometimes it may be hard to tell the difference — and this leads to my doubts:

  • Given that coordination is hard, gaining knowledge is expensive, and optimization path dependent, the entities and movements I criticize may not have room to improve, at least not in the direction I want them to improve in. The cost of making “more fulsome and coordinated” true might be greater than mutual reinforcement and other gains.
  • See the second doubt in the previous section — competition from the commons might be futile. Rather than promoting them at every turn, they should sometimes be held up as victims of bad policy, to be protected, and sometimes hidden from policy discourse.

The first doubt is surely merited, at least for many entities on many issues. For any criticism I have in this space, it makes sense to give the criticized the benefit of the doubt; they know their constraints pretty well, while I’m just making abstract speculations. Still, I think it’s worthwhile to call for more fulsome and coordinated strategy in the interstices of these movements, e.g., conversation and even this blog, in the hope of long-term learning, played out over years in existing entities and movements, and new ones. I will try henceforth to do so more often in a “big picture” way, or through example, and less often through criticism of specific choices made by specific entities — in retrospect the stream of the latter on this blog over the last year has been tedious.

International Apartheid

For example: Abolish Foreignness, Do we have any scrap of evidence that [the Chinese Exclusion Act] made us better off?, and Opposing “illegal” immigration is xenophobic, or more bluntly, advocating for apartheid “because it’s the law”. I hinted at a subtheme about the role of cities, to be filled out later.

The system is grossly unjust and ought be abolished, about that I have no doubt. Existing institutions and arrangements must adapt. But, two doubts about my approach:

  • Too little expression of empathy with those who assume the goodness of current policy. Fear of change, competition, “other” are all deep. Too little about how current unjust system can be unwound in a way the mitigates any reality behind these fears. Too little about how benefits attributed to current unjust system can be maintained under a freedom respecting regime. (This doubt also applies to the intellectual freedom theme.)
  • Figuring out development might be more feasible, and certainly would have more impact on human welfare, individual autonomy, than smashing the international apartheid system. Local improvements to education, business, governance, are what all ought focus on — though development economics has a dismal record, it at least has the right target. Migration is a sideshow.

As with the intellectual freedom theme, these doubts merit engagement, and such will strengthen the case for freedom. But even moreso than in the case of intellectual freedom infringing regimes, the unconscionable and murderous injustice of the international apartheid regime must be condemned from the rooftops. It is sickening and unproductive to allow discourse on this topic to proceed as if the regime is anything but an abomination, however unfeasible its destruction may seem in the short term.

Politics

Although much of what I write here can be deemed political, one political theme not subsumed by others is inadequate self-regulation of the government “market”, e.g., What to do about democratically elected terrorist regimes, Suppose they gave a war on terror and a few exposed it as terror, and Why does the U.S. federal government permit negative sum competition among U.S. states and localities?

The main problem with this theme is omission rather than doubt — no solutions proposed. Had I done so, I’d have plenty to doubt.

Refutation

I fell behind, doing refuting only posts from first and second quarters of 2005. My doubt about this enjoyable exercise is that it is too contrived. Many of the refutations are flippant and don’t reflect any real doubts or knowledge gained in the last 8 years. That doubt is what led me to the exercise of this post. How did I do?

Clubbing out of the vicious circle of bad policy (patents)

Thursday, January 2nd, 2014

Glyn Moody in Defensive Patent Licence: Nice Idea; Not Much Use:

The rest of Linksvayer’s thoughtful post explores these ideas and their background, and in particular looks at how they fit with other aspects of free software.

My fascinating post (thanks).

It’s well worth reading, even if the DPL itself is likely to have relatively little impact. That’s because it only applies to those who join the DPL club, which creates a typical vicious circle: few entities in the club to start with mean that few patents are made available on an royalty-free basis, and so there’s little incentive for more entities to join.

The vicious cycle can be overcome. Joining the club is very low barrier: gratis, and an entity doesn’t even have to hold any patents. Royalty-free patents from club members is only part of the reason for joining. Another is expression — taking advantage of the patent skepticism of many people, and exploiting for ethical branding and recruitment. These patent pool and expressive incentives could be mutually re-enforcing: the more entities join, the larger the pool, and the stronger the expectation that non-evil entities join.

Whether the vicious cycle will be overcome comes down to sales. The DPL people have put in place a lot of groundwork that will help — seemingly a large amount of work by credible people into making the DPL a robust legal instrument, a credible group of people as advisors (and presumably an impressive board when it reaches that stage), presumably some amount of funding. This combination of gravitas and resources would make it possible for a tireless campaigner (the pre-conditions do remind me of Creative Commons, whose tireless campaigner was Lawrence Lessig) or sales team befitting the target market to succeed in getting lots of entities to join the club.

One indicator after the DPL’s public launch next month will be whether the next columns and stories by journalists continue to focus on the barrier of lack of network effects, or on celebrating early joiners and urging other entities to follow as an urgent matter of public policy or industry best practice. This will be an indicator in large part because the DPL people’s efforts right now can shape these stories.

Still, it’s nice to see people thinking innovatively in this space as we work towards the ultimate goal of full abolition of software patents everywhere.

Indeed, though the DPL applies to all patents, and all patents everywhere should be fully abolished, as I’m pretty sure Moody agrees (but probably not the DPL people; that’s OK, they made a useful tool).

You can attend the DPL launch conference in Berkeley: February 28November 7, 2014, gratis registration. Your organization should join the club, now!

Video of the DPL birthday is up on the Internet Archive.

Happy GNU Year & Public Domain Day

Wednesday, January 1st, 2014
happy gnu year and public domain day

Any previous combinations? Reminded of GNU year greetings by Laurel Russwurm and Public Domain Day by the Public Domain Review and Center for the Study of the Public Domain.

My previous Public Domain Day posts:

Echoing the 2011 entry, I recently urged all to upgrade to CC0 (a public domain dedication and license). Also, January 1 is a good date to reiterate:

Unless stated otherwise, everything by me, Mike Linksvayer, published anywhere, is hereby placed in the public domain.

Join me. More importantly, unless you’re prodigious, demand that at the very least all government material go directly into the public domain.

The bottom part of the image is from The Gnoo (1804) by Samuel Daniell (1775-1811). The top is from an illustration (1883) by Louis-Maurice Boutet de Monvel (1851-1913). Latter selected because it is newly unambiguously in the public domain worldwide, including Mexico, which has life + 100 years of restriction. It would not be shocking to see this term ratchet worldwide in the next years.

Bonus links: