User:Cjl/SandboxGlossary: Difference between revisions
m (Walter's rectum 23/SandboxGlossary moved to User:Cjl/SandboxGlossary over redirect: revert) |
|||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
Spanish Health Content Dash |
|||
Proposal for Keyboard page naming and categorization conventions |
|||
a Pre-Fab Fortnight. . . |
|||
The goal of this page is to promote discussion aimed at producing a consensus on a clear and easily understood convention for the naming of keyboard pages and for some basic standards for applying categories to those pages all in the service of improving the navigation between pages related to country, local OLPC chapter, language and script. |
|||
It's not the sprint of a Jam and it's not the marathon of development from scratch on the wiki. . . |
|||
The purpose is to give the Health effort some intensive short-term focus aimed at getting content into the Repository that can immediately be offered to schools in Spanish-speaking deployments (e.g. Peru) right away. There is no question that health content is needed in all languages currently in active deployment, but this is a concerted push for "low-hanging fruit". This will serve to gather materials that can be considered for translation into other languages, but we must gather them first and that is what this effort is all about. |
|||
==Background== |
|||
The goal is to target health-related content that meets some very specific criteria. |
|||
This discussion originated on this [[User_talk:CharlesMerriam | User_talk]] page. On this wiki, there is sometimes confusing usage of "OLPC" as a prefix/suffix. There is a general pattern of naming keyboard pages in the pattern of "OLPC ''language/script'' keyboard" which reads as "OLPC (Cambridge) keyboard design for ''language/script''". |
|||
1) Immediately available, currently posted online (no scanning, software or hardware development effort to undertake). |
|||
In addition there are many pages and categories in the pattern of "OLPC ''country''", which is perhaps best read as "OLPC volunteers in ''country''", although it may be confused as being more narrowly defined as the local chapter organized with the name "OLPC ''country''". It would seem that the narrower construction emphasizes the organization over cooperative and hopefully coordinated efforts. [[OLPC Nepal]] and [[OLE_Nepal]] offer an example where there are two local organizations working on OLPC deployment in Nepal. Tagging an OLE Nepal developed page with the category "OLPC Nepal" would hopefully not be seen as improperly crediting OLE Nepal's worthy efforts, but rather it should be seen as a way to allow newcomers to more easily navigate (using category tags) to all of the pages related to the efforts (of all parties) to help children in Nepal by deploying XO laptops and XS servers and related content efforts. |
|||
Preferred file formats (define with specific extensions) (HTML, PDF, Flash. . . ) |
|||
2) Available under suitable licensing terms. (define). |
|||
[http://olpc-ceibal.blogspot.com/ Proyecto Ceibal] (also sometimes known as OLPC Ceibal or on this wiki as [[OLPC_Uruguay]]) offers an example where a local organization does not choose the "English-standard" "OLPC ''country''" naming convention. Through it's efforts, OLPC embraces localization into many languages and local organizations are, of course, free to name themselves as they choose; however, it is to be expected that english-language users on the wiki will generally look for the english language pages related to a given country's OLPC efforts at the "OLPC ''country''" page. |
|||
3) Available in Spanish (ideally also in English). Purpose: Postpone the challenge of recruiting sufficient multilingual subject matter experts. Having an example content bundle to show is going to be a big help bring them in over time. |
|||
4) Made available from an acknowledged authority in the relevant field, e.g. transnational or local government agency (PAHO, WHO, local Ministry of Health), well-known health advocacy NGO, etc.. |
|||
To add to the confusion, there are also many pages employing the naming pattern of "OLPC ''city/region''". This is seen mostly in the North America where the G1G1 program has resulted in many XO laptops in the hands of folks in various metro areas, where they have organized themselves under "OLPC ''city/region''" banners for meet-ups to explore the XO together and also to coordinate contributions to the broader OLPC effort. These pages generally have the "XO User Group" category tag. |
|||
The point of this is that these materials can generally be expected to have undergone a substantial level of subject matter expert review and if this content is not specifically posted under suitable licensing terms, the liklihood of having prdcutive exchange wit hthe organization about |
|||
== Options for improving navigation== |
|||
[[User:CharlesMerriam | Charles Merriam]] has been developing a template page that may offer a technical solution to some of these cross-referencing issues with regard to country and keyboard. |
|||
Set priorities by objective measures (e.g. http://www.dcp2.org/page/main/Home.html) |
|||
<Charles to insert template references and discussion here> |
|||
==Naming Proposal== |
|||
Walk through full process: Licensing review, Pedogological review, Subject Matter Expert review, Localization process, Bundle generation |
|||
Keyboard pages will generally be named in the form "OLPC ''language/script'' keyboard". |
|||
Keyboard pages should generally include relevant "OLPC ''country''" category tags to improve navigation from the "OLPC ''country''" pages. |
|||
Exceptions to these conventions are to be expected where it would lead to confusion. |
|||
Real trick is finding bilingual subject matter experts for translation and review, using pre-translated materials from authoritative sources (e.g. PAHO, WHO, etc.) certainly quicker. |
|||
Quick route to medical education content is to frame OLPC content bundle as a great "platform/channel" for distribution. School authorities will ultimately choose content that goes on school server, so MinHealth or PAHO materials will more-or-less have "pre-approved" stamp on them. |
|||
==Specific actions proposed== |
|||
Could recruit here |
|||
<cjl to list out all all keyboard pages and proposed name changes (if needed)> |
|||
#OLPC Argentina Keyboard |
|||
#OLPC Armenian Keyboard |
|||
#OLPC Brasil Keyboard |
|||
#OLPC Cyrillic Keyboard |
|||
#OLPC Dari Keyboard |
|||
#OLPC Devanagari Keyboard |
|||
#OLPC Ethiopia Keyboard |
|||
#OLPC French Canadian Keyboard |
|||
#OLPC Italian Keyboard |
|||
#OLPC Kazakh Keyboard |
|||
#OLPC Khmer Keyboard |
|||
#OLPC Libya Keyboard |
|||
#OLPC Mongolian Keyboard |
|||
#OLPC Nepal Keyboard |
|||
#OLPC Nigeria Keyboard |
|||
#OLPC Pakistan Keyboard |
|||
#OLPC Pashto Keyboard |
|||
#OLPC Pulaar Keyboard |
|||
#OLPC Rwanda Keyboard |
|||
#OLPC Thailand Keyboard |
|||
#OLPC Turkey Keyboard |
|||
#OLPC Turkey Q-Type Keyboard |
|||
#OLPC Urdu Keyboard |
|||
#OLPC US International Keyboard |
|||
#OLPC Uzbek Keyboard |
|||
http://www.paho.org/English/DD/IKM/eq-list.htm PAHO Equity, Health and Human Development Listserve |
|||
Peru PAHO http://www.per.ops-oms.org/ |
|||
<Also to list proposed "OLPC ''country''" tags for each for review> |
|||
Latest revision as of 15:32, 20 December 2009
Spanish Health Content Dash
a Pre-Fab Fortnight. . .
It's not the sprint of a Jam and it's not the marathon of development from scratch on the wiki. . .
The purpose is to give the Health effort some intensive short-term focus aimed at getting content into the Repository that can immediately be offered to schools in Spanish-speaking deployments (e.g. Peru) right away. There is no question that health content is needed in all languages currently in active deployment, but this is a concerted push for "low-hanging fruit". This will serve to gather materials that can be considered for translation into other languages, but we must gather them first and that is what this effort is all about.
The goal is to target health-related content that meets some very specific criteria.
1) Immediately available, currently posted online (no scanning, software or hardware development effort to undertake).
Preferred file formats (define with specific extensions) (HTML, PDF, Flash. . . )
2) Available under suitable licensing terms. (define).
3) Available in Spanish (ideally also in English). Purpose: Postpone the challenge of recruiting sufficient multilingual subject matter experts. Having an example content bundle to show is going to be a big help bring them in over time.
4) Made available from an acknowledged authority in the relevant field, e.g. transnational or local government agency (PAHO, WHO, local Ministry of Health), well-known health advocacy NGO, etc..
The point of this is that these materials can generally be expected to have undergone a substantial level of subject matter expert review and if this content is not specifically posted under suitable licensing terms, the liklihood of having prdcutive exchange wit hthe organization about
Set priorities by objective measures (e.g. http://www.dcp2.org/page/main/Home.html)
Walk through full process: Licensing review, Pedogological review, Subject Matter Expert review, Localization process, Bundle generation
Real trick is finding bilingual subject matter experts for translation and review, using pre-translated materials from authoritative sources (e.g. PAHO, WHO, etc.) certainly quicker.
Quick route to medical education content is to frame OLPC content bundle as a great "platform/channel" for distribution. School authorities will ultimately choose content that goes on school server, so MinHealth or PAHO materials will more-or-less have "pre-approved" stamp on them.
Could recruit here
http://www.paho.org/English/DD/IKM/eq-list.htm PAHO Equity, Health and Human Development Listserve
Peru PAHO http://www.per.ops-oms.org/