Roadmap for development for the Advanced Custom Fields plugin for WordPress.
The Social Benefits of a Public Roadmap
Reply
Tag Archives: Open Source
Comment on Open Source development at NASA
A comment on: http://open.nasa.gov/blog/2011/09/08/open-source-development-at-nasa/
I am all for OpenData and Open.NASA. But how does NASA being a government entity relate to how it “licenses” it’s data and software? What I mean is that, shouldn’t the things being “open sourced” be public domain, rather than licensed content? I agree that creating a license which is not widely recognized is not useful, that is the whole point behind Creative Commons. But are there cases where NASA is “over licensing” content that it shouldn’t because it is the content should be released into the public domain? Reference CC Salon in Jan 2011, Time segment 1:05:00 where Joi Ito talks about the issue. http://blip.tv/creative-commons/creative-commons-salon-mountain-view-what-does-it-mean-to-be-open-in-a-data-driven-world-4725230
What prevents, or what reasons are there for not putting NASA’s data and software, which it releases, in the public domain? Is that not more open?
Open Change
I was recently looking at licenses for databases and discovered the ODbL license. This license was pioneered by the OpenStreetMap Project. I was reading their introduction to why the change was needed. This introduction outlined what the change was, what the change would allow them to do, who agreed, who disagreed, what the cost of the change would be, among other things. I thought it was a very open, engaging and confidence building way to move a group of volunteers through change. It allows for more kinds (also different kinds) of product use. It is well worth the look at not only if you are interested in the open licensing of data in databases and why CC-BY-SA and CC0 licenses do not work for data [also as PDF], but also how they are answering the questions of the community as they are moving the community through change.
Open Source Language Codes Meta-data
One of the projects I have been involved with published a paper this week in JIPA. It is a first for me; being published. Being the thoughtful person I am, I was considering how this paper will be categorized by librarians. For the most part papers themselves are not catalogued. Rather journals are catalogued. In a sense this is reasonable considering all the additional meta-data librarians would have to create in their meta-data tracking systems. However, in today’s world of computer catalogues it is really a shame that a user can’t go to a library catalogue and say what resources are related to German [deu]? As a language and linguistics researcher I would like to quickly reference all the titles in a library or collection which reference a particular language. The use of the ISO 639-3 standard can and does help with this. OLAC also tires to help with this resource location problem by aggregating the tagged contents of participating libraries. But in our case the paper makes reference to over 15 languages via ISO 639-3 codes. So our paper should have at least those 15 codes in its meta-data entry. Furthermore, there is no way for independent researchers to list their resource in the OLAC aggregation of resources. That is, I can not go to the OLAC website and add my citation and connect it to a particular language code.
There is one more twist which I noticed today too. One of the ISO codes is already out of date. This could be conceived of as a publication error. But even if the ISO had made its change after our paper was published then this issue would still be persistent.
During the course of the research and publication process of our paper, change request 2009-78 was accepted by the ISO 639-3 Registrar. This is actually a good thing. (I really am pro ISO 639-3.)
Basically, Buhi’non Bikol is now considered a distinct language and has been assigned the code [ubl]. It was formerly considered to be a variety of Albay Bicolano [bhk]. As a result of this change [bhk] has now been retired.
Here is where we use the old code, on page 208 we say:
voiced velar fricative [ɣ]
- Aklanon [AKL] (Scheerer 1920, Ryder 1940, de la Cruz & Zorc 1968, Payne 1978, Zorc 1995) (Zorc 1995: 344 considers the sound a velar approximant)
- Buhi’non [BHK] (McFarland 1974)
In reality McFarland did not reference the ISO code in 1974. (ISO 639-3 didn’t exist yet!) So the persistent information is that it was the language Buhi’non. I am not so concerned with errata or getting the publication to be corrected. What I want is for people to be able to find this resource when they are looking for it. (And that includes searches which are looking for a resource based on the languages which that resource references.)
The bottom line is that the ISO does change. And when it does change we can start referencing our new publications and data to the current codes. But there are going to be thousands of libraries out there with out-dated language codes referencing older publications. A librarian’s perspective might say that they need to add both the old and the new codes to the card catalogues. This is probably the best way to go about this. But who will notice that the catalogues need to be updated with the new codes? What this change makes me think is that there needs to be an Open Source vehicle where linguists and language researchers can give their knowledge about a language resources a community. Then librarians can pull that meta-data from that community. The community needs to be able to vet the meta-data so that the librarians feel like it is credible meta-data. In this way the quality and relevance of Meta-data can always be improved upon.
Radiant a CMS developed in Ruby
I was browsing – cause that is what I do. – And I came across this very flexible, yet young CMS. :: http://radiantcms.org/
One of the cool things that I liked off the bat:
- Update the data on display from an XML feed.
I immediately thought of a site I consulted for : scriptureearth.org that this could be a solution for that. (The site is in production but I am not sure how easy it is to update the data it displays. The connivence of a XML feed is that the site would be able to be updated from an app based in the workflow of the publisher.)