In the U.S. we have a long tradition of citizenry, police, and military. For many years the citizenry has had distinct semantic categories for these social functions. However, I think there is evidence that at some levels these distinctions are merging. While not all citizens agree that the merger is useful, it is nevertheless happening at a political and managerial level. Terms like Law Enforcement extend beyond the traditional roles of police and bring the police into a larger strategically orchestrated social movement. In addition to this some of the traditional imagery surrounding police has changed. While it does raise many questions about the order and structure of society in the U.S. one question which seems pertinent to ask is: Who is protected and Who is served?
More Traditional Police imagery.
More modern police imagery.
More modern police imagery.
Imagery is only one way to assess the conflation of semantic concepts. Another way to look at it would be to consider concepts and terminology of detainees and prisoners as those concepts are practiced by Law Enforcement operators. A look at the U.S. Army's Internment and Resettlement manual's terminology found in FM 3-39.40 available at http://armypubs.army.mil/doctrine/19_Series_Collection_1.html or locally [PDF]
As linguistics and language documentation interface with digital humanities there has been a lot of effort to time-align texts and audio/video materials. At one level this is rather trivial to do and has the backing of comercial media processes like subtitles in movies. However, at another level this task is often done in XML for every project (digital corpus curation) slightly differently. At the macro-scale the argument is that if the annotation of the audio is in XML and someone wants to do something else with it, then they can just convert the XML to whatever schema they desire. This is true.
However, one antidotal point that I have not heard in discussion of time aligned texts is specifications for Audio Dominant Text vs. Text Dominant Audio. This may not initially seem very important, so let me explain what I mean. Continue reading →
In my work with redesigning a NGO’s website, I have been recommending that the organization adopt and implement an engagement strategy. There are several challenges to this.
There is the question: What is an engagement strategy which we are not doing now? Basically, what is the difference between engagement strategy and operations. – and certainly these are areas of organizations which need to have some symbiotic relationship.
Another question has been: Why do we need an engagement strategy with our new website? – The new website is centrally managed, whereas operations are generally regionally managed.
So, the over simplistic answer is that if what a corporation presents themself as on their website is something which they are operationally not, then that presents certain discontinuities for persons viewing their operations and also viewing their website. This becomes evermore important as many potential clients for organizations first interact with that organization via the web. I first started blogging about engagement with regards to Language Development activities in a post titled: The Look of Language Development Websites.
However, engagement strategy goes beyond just presenting continuity. It gets into connecting potential clients with services offered or knowledge held by that organization. An engagement strategy for an NGO with a cause also speaks to how that NGO is going to target persons who are not aware of their cause and introduce them to the cause and provide options for those newly introduced persons to become part of a great solution for the problem just presented. This level of engagement is different than Public Relations, or brochure development (though both of these can be part of an engagement strategy). Continue reading →
When I was in México, working with a team doing language documentation we visited a community workshop where the community organizer was promoting the language through a dictionary creation effort. I was interesting to see the various bi-lingual teachers come together and discuss a proposed entry and the definition.
Meꞌphaa group working on dictionary
There were several interesting aspects of the social interaction: there was the political unity in the perception that they were all there for the good of their language, there was the social unity because they were mostly there because they were in state jobs as teachers or school administrators. But perhaps more socially significant was the perception that the workshop leader had skills in organizing a dictionary. (Nothing wrong with this perception and it is probably an accurate perception.) Yet, it was not the only perception which was at play in the social interactions. There was also the cultural age based and social ranking based way of coming to a consensus about what did a particular Meꞌphaa (or any given) word mean. It is kind of this unspoken tension between the eldest in the group who would culturally have the authority or provide a stamp of approval, the workshop "dictionary expert", and the average participant who has to decide if they agree or disagree with whom and if they are going to show it. Continue reading →
I have been working on describing the FLEx software eco-system (for both a blog post and an info-graphic). In the process I googled "language documentation" workflow and was promptly directed to resources created for InField and aggregated via ctldc.org. An amazing set of resources. the ctldc.org website is well put together and the content from InField 2010 and 2008 is amazing - I which I could have been there. I am almost convinced that most SIL staff pursuing linguistic fieldwork should just go to InField... But it is true that InField seems to be targeted at someone who has had more than one semester of linguistics training.
In the open source development world there is a lot of emphases on developing software to solve specific problems, there is much less emphasis on solving those problems well. That is, solving those problems so the most people are serviced, or so that users of software have the flexibility they need (there is also often a lack of commitment to User Experience Design but this is a shameless side plug). And there is often a real lack of collaboration around competing solutions. This is evident in the software which is created for use by linguists (usually also coded by linguists for solving the linguists’ challenges) but this is also evidenced in a different sphere of programing in the WordPress eco-system. In the WordPress eco-system there is a plethora of plugins which are abandoned. WordPress is GPL’d and so these plugins are GPL’d too. However, the repository – the human visual interface to the repository – allows for coders to grab code, and modify it for their ends, but it doesn’t allow for merging once the plugin has been “updated”. (It is true that not all changes are “updates”, sometimes people need one-off solutions.) But the net result is that early 1/3rd of all plugins for wordpress are abandoned. Their developer has been paid and has now ended their relationship with the commissioning client, or the WordPress eco-system no-longer requires the service options provided by that plugin. Matt Jones created an info-graphic to illustrate this point and to bring awareness to the problem. My comments below are my reply to him, with some minor corrections . Continue reading →