From joachim.wackerow at gesis.org Thu Nov 5 02:51:51 2009 From: joachim.wackerow at gesis.org (Joachim Wackerow) Date: Thu, 05 Nov 2009 08:51:51 +0100 Subject: [DDI-users] Call for Participation: 1st Annual European DDI Users Group Meeting Message-ID: <4AF28417.3050301@gesis.org> 1st Annual European DDI Users Group Meeting DDI - The Basis of Managing the Data Life Cycle December 3 - 4, 2009, Bonn, Germany Hosted by the International Data Service Center (IDSC) of IZA. Workshop at December 3 afternoon Course on DDI 3: Putting DDI to Work for You (Wendy Thomas, University of Minnesota, Minnesota Population Center) Conference program at December 4 Opening plenary talk Kevin Sch?rer, Director of the Economic and Social Data Service (ESDS) and the UK Data Archive (UKDA): Why DDI must succeed and the perils of it not doing so. Accepted Talks - Alerk Amin (CentERdata): Questasy - Case Study - Ingo Barkow (DIPF - Deusches Institut f?r Internationale P?dagogische Forschung): Usage of a DDI structure in the NEPS Data Warehouse - Martin Friedrichs (GESIS - Leibniz Institute for the Social Sciences): The case of CHARMCATS: Use of DDI3 for publishing harmonisation routines - Rob Grim (Tilburg University): The EVS and NKO subject portal for enhanced publications: connecting archives and libraries with DDI - Matti Heinonen/Mari Kleemola (Finnish Social Science Data Archive): Evaluation of DDI3: marking-up ISSP 2006 Finnish data - Jannik Jensen (Danish Data Archive): Editing DDI - Uwe Jensen (GESIS - Leibniz Institute for the Social Sciences): DDI 3 and re-use of metadata in archival processes - Uwe Jensen (GESIS - Leibniz Institute for the Social Sciences): Considerations to support and implement DDI 3 in building the cessda-ERIC - Simon Jones/Paul Lambert (University of Stirling): Metadata Creation, Transformation and Discovery for Social Science Data Management: The DAMES Project Infrastructure - Meinhard Moschner (GESIS - Leibniz Institute for the Social Sciences): Controlled vocabularies for DDI3 - a work in progress - Marika Puumala (CentERdata): How to Present an Application Based on DDI 3 to the World Out There? -Experiences from a project in which we have built an online survey data dissemination application based on DDI 3 - Humphrey Southall (University of Portsmouth): Creating DDI Metadata for a diverse body of aggregate statistics: Experience with the GB Historical GIS - Karsten Stephan (Higher Education Information System (HIS)): Using a DDI 3 Based Single Source Approach to Increase the Efficiency of Social Science Research Processes - Andias Wira-Alam (GESIS - Leibniz Institute for the Social Sciences): Implementing DDI 3.0 : a case study of the German Microsensus - Denis Huschka (German Council for Social and Economic Data (RatSWD)): Developments of the Research Data Infrastructure in Germany since the end of the 90's If you are interested in participating in the conference, please send an email to Mr. Stephan Kohzer (kohzer at iza.org). Accommodation and directions information at: http://www.iza.org/conference_files/eddi09/2009_11_03_logistics.pdf The full program including abstracts and further information are available at: http://www.iza.org/eddi09 EDDI 2009 is organized jointly by the Institute for the Study of Labor (IZA) and GESIS - Leibniz Institute for the Social Sciences. The event is supported by the German Council for Social and Economic Data (RatSWD). The poster of the event may be found here: http://www.ddialliance.org/ddi-europe-2009.pdf Nikos Askitas Joachim Wackerow (Organizers) From Klaus.Pforr at mzes.uni-mannheim.de Wed Nov 11 09:52:55 2009 From: Klaus.Pforr at mzes.uni-mannheim.de (Klaus Pforr) Date: Wed, 11 Nov 2009 15:52:55 +0100 Subject: [DDI-users] Using Groups to manage frequent questionnaire versions Message-ID: <4AFACFC7.8010504@mzes.uni-mannheim.de> Hello, I'm beginning to plan to document a complex panel study (http://www.pairfam.uni-bremen.de/index.php?id=2&L=1) with DDI and have a question about how to use groups. It is certainly reasonable to organize the different waves as children of one higher level group, where the changes in each wave are overriders of a default version. In our project we have the problem of organizing many versions in the questionnaire design process of each wave. Is it reasonable to organize these versions also with groups? I think about placing the things that are generally agreed on as group level info and the version changes at the child-level. Best regards Klaus Pforr -- __________________________________ Klaus Pforr MZES AB - A Universit?t Mannheim D - 68131 Mannheim Tel: +49-621-181 2801 (nachmittags) fax: +49-621-181 2803 URL: http://www.mzes.uni-mannheim.de Besucheranschrift: A5, Raum A312 __________________________________ From wlt at pop.umn.edu Wed Nov 11 11:19:41 2009 From: wlt at pop.umn.edu (Wendy Thomas) Date: Wed, 11 Nov 2009 10:19:41 -0600 (CST) Subject: [DDI-users] Using Groups to manage frequent questionnaire versions In-Reply-To: <4AFACFC7.8010504@mzes.uni-mannheim.de> References: <4AFACFC7.8010504@mzes.uni-mannheim.de> Message-ID: Dear Klaus, This came up frequently in a recent Expert Workshop at Dagstuhl and will be the subject of 2-3 of the Use Cases arising out of it. Basically there are a number of approaches to grouping in terms of how to determine what the primary tree structure will be. From the discussions at Dagstuhl there are a few primary considerations: 1) What is the most stable information? Least stable information? You will want those parts that remain the most stable near the top of the tree and the least stable near the bottom. For example, in the integrated ISSP example we had, the content of the modules (topical questions/variables) were the primary grouping (first level of subgroups) because this was the most stable content and primary approach for the researchers who would be served. The next level was Country (geography), then time (least stable). 2) What is the primary approach to the data? In the above example it was topical module. However, in another example using the ISSP, the concern was to manage the production process within a single country so that the focus was on time rather than topic. Both approaches work, but each facilitates a different usage. 3) In the case you mention below, if I am understanding it, you want to capture the development process of a questionnaire as well as the final questionnaire used in data collection. You could capture the development process (change in content) either by grouping as you noted or by versioning the content of your question schemes and control contstruct schemes. I think it would help to see an example of what you are trying to capture. I think you are saying you have the following situation, but I'm not clear. Wave I: Start with Original content Versioning during design process resulting in Wave I: content X Wave II: Start with Wave I: content X content Versioning during design process resulting in Wave II: content Y Wave III: Start with Wave II: content Y content Versioning during design process resulting in Wave III: content Z Etc. Is this correct? Do waves have different content (other than revisions due to development) such as topical changes? As an aside, please note that there is additional structure being developed to capture the questionnaire development process which you probably want to follow. Wendy On Wed, 11 Nov 2009, Klaus Pforr wrote: > Hello, > > I'm beginning to plan to document a complex panel study > (http://www.pairfam.uni-bremen.de/index.php?id=2&L=1) with DDI and have > a question about how to use groups. It is certainly reasonable to > organize the different waves as children of one higher level group, > where the changes in each wave are overriders of a default version. > > In our project we have the problem of organizing many versions in the > questionnaire design process of each wave. Is it reasonable to organize > these versions also with groups? > I think about placing the things that are generally agreed on as group > level info and the version changes at the child-level. > > Best regards > > Klaus Pforr > -- > __________________________________ > > Klaus Pforr > MZES AB - A > Universit?t Mannheim > D - 68131 Mannheim > Tel: +49-621-181 2801 (nachmittags) > fax: +49-621-181 2803 > URL: http://www.mzes.uni-mannheim.de > > Besucheranschrift: A5, Raum A312 > __________________________________ > _______________________________________________ > DDI-users mailing list > DDI-users at icpsr.umich.edu > http://www.icpsr.umich.edu/mailman/listinfo/ddi-users > Wendy L. Thomas Phone: +1 612.624.4389 Data Access Core Director Fax: +1 612.626.8375 Minnesota Population Center Email: wlt at pop.umn.edu University of Minnesota 50 Willey Hall 225 19th Avenue South Minneapolis, MN 55455 From Klaus.Pforr at mzes.uni-mannheim.de Wed Nov 11 12:00:54 2009 From: Klaus.Pforr at mzes.uni-mannheim.de (Klaus Pforr) Date: Wed, 11 Nov 2009 18:00:54 +0100 Subject: [DDI-users] Using Groups to manage frequent questionnaire versions In-Reply-To: References: <4AFACFC7.8010504@mzes.uni-mannheim.de> Message-ID: <4AFAEDC6.4090206@mzes.uni-mannheim.de> Dear Wendy, Thank you for reminding me of the very helpful overall tree organization rule (most stable topmost, least stable to the bottom). You guessed pretty much right. Although we have mostly constant modules across waves, especially in the first 3-4 waves we have new modules and item changes. These changes cause the most amount of work. Your suggested structure seems to be a good starting point. Klaus Wendy Thomas schrieb: > Dear Klaus, > > This came up frequently in a recent Expert Workshop at Dagstuhl and will > be the subject of 2-3 of the Use Cases arising out of it. Basically > there are a number of approaches to grouping in terms of how to > determine what the primary tree structure will be. From the discussions > at Dagstuhl there are a few primary considerations: > > 1) What is the most stable information? Least stable information? > You will want those parts that remain the most stable near the top of > the tree and the least stable near the bottom. For example, in the > integrated ISSP example we had, the content of the modules (topical > questions/variables) were the primary grouping (first level of > subgroups) because this was the most stable content and primary approach > for the researchers who would be served. The next level was Country > (geography), then time (least stable). > > 2) What is the primary approach to the data? In the above example it was > topical module. However, in another example using the ISSP, the concern > was to manage the production process within a single country so that the > focus was on time rather than topic. Both approaches work, but each > facilitates a different usage. > > 3) In the case you mention below, if I am understanding it, you want to > capture the development process of a questionnaire as well as the final > questionnaire used in data collection. You could capture the development > process (change in content) either by grouping as you noted or by > versioning the content of your question schemes and control contstruct > schemes. > > I think it would help to see an example of what you are trying to > capture. I think you are saying you have the following situation, but > I'm not clear. > > Wave I: Start with Original content > Versioning during design process resulting in Wave I: content X > > Wave II: Start with Wave I: content X content > Versioning during design process resulting in Wave II: content Y > > Wave III: Start with Wave II: content Y content > Versioning during design process resulting in Wave III: content Z > > Etc. > > Is this correct? Do waves have different content (other than revisions > due to development) such as topical changes? > > As an aside, please note that there is additional structure being > developed to capture the questionnaire development process which you > probably want to follow. > > Wendy > > > On Wed, 11 Nov 2009, Klaus Pforr wrote: > >> Hello, >> >> I'm beginning to plan to document a complex panel study >> (http://www.pairfam.uni-bremen.de/index.php?id=2&L=1) with DDI and have >> a question about how to use groups. It is certainly reasonable to >> organize the different waves as children of one higher level group, >> where the changes in each wave are overriders of a default version. >> >> In our project we have the problem of organizing many versions in the >> questionnaire design process of each wave. Is it reasonable to organize >> these versions also with groups? >> I think about placing the things that are generally agreed on as group >> level info and the version changes at the child-level. >> >> Best regards >> >> Klaus Pforr >> -- >> __________________________________ >> >> Klaus Pforr >> MZES AB - A >> Universit?t Mannheim >> D - 68131 Mannheim >> Tel: +49-621-181 2801 (nachmittags) >> fax: +49-621-181 2803 >> URL: http://www.mzes.uni-mannheim.de >> >> Besucheranschrift: A5, Raum A312 >> __________________________________ >> _______________________________________________ >> DDI-users mailing list >> DDI-users at icpsr.umich.edu >> http://www.icpsr.umich.edu/mailman/listinfo/ddi-users >> > > Wendy L. Thomas Phone: +1 612.624.4389 > Data Access Core Director Fax: +1 612.626.8375 > Minnesota Population Center Email: wlt at pop.umn.edu > University of Minnesota > 50 Willey Hall > 225 19th Avenue South > Minneapolis, MN 55455 > > > ------------------------------------------------------------------------ > > _______________________________________________ > DDI-users mailing list > DDI-users at icpsr.umich.edu > http://www.icpsr.umich.edu/mailman/listinfo/ddi-users -- __________________________________ Klaus Pforr MZES AB - A Universit?t Mannheim D - 68131 Mannheim Tel: +49-621-181 2801 (nachmittags) fax: +49-621-181 2803 URL: http://www.mzes.uni-mannheim.de Besucheranschrift: A5, Raum A312 __________________________________ From mcneillh at MIT.EDU Wed Nov 18 14:19:05 2009 From: mcneillh at MIT.EDU (Katherine McNeill) Date: Wed, 18 Nov 2009 14:19:05 -0500 Subject: [DDI-users] [DDI-UOG-Chair] Adopting DDI for a survey In-Reply-To: References: Message-ID: <25C6BB73D3916546AD374E64735FC7080BF65BC5@EXPO12.exchange.mit.edu> Stein, Thank you for your interest, and I'm also forwarding your message to the DDI Users email list, where other users (many of whom I know have experience in Blaise) can respond to your question as well. There is a particular section of the DDI that would be use to document the variables (specifically in the logical product module: http://gandalf.opendatafoundation.org/infocenter/topic/net.sf.ddialliance.help/html/modules/ddi3_logicalproduct.html), whereas most of the other elements document other contextual information about the data (collection, storage formats, etc.). As for tools, there's a simple DDI editor tool at: http://www.ddialliance.org/DDI/ddi3/editor-lite-3/DDI_v2dot2.html Within the DDI Tools project page (http://tools.ddialliance.org/?lvl1=library) you can view a list of XML examples, and the first one in the list shows examples of markup of variables. And I believe that others who respond to your question will be able to provide even more detailed guidance. Sincerely, Katherine McNeill From: ddi-uog-chair-bounces at ddialliance.org [mailto:ddi-uog-chair-bounces at ddialliance.org] On Behalf Of Steinberg Tan Sent: Tuesday, November 17, 2009 9:37 PM To: ddi-uog-chair at icpsr.umich.edu Cc: Steinberg Tan Subject: [DDI-UOG-Chair] Adopting DDI for a survey Hi, My name's Steinberg and I work for the Australian Bureau of Statistics. I am currently involved in a pilot project to see if we can map a small survey to DDI standard. I've been reading some of the papers and presentations on the net but am still a bit confused about how we go about mapping it. Our current system (end-to-end system) consists of various components from our data store (star schema) to Blaise (edits and data entry) and many others in-between. For this pilot project, our initial goal is to map every variable in the survey form to DDI - I'm writing to ask if there are any tools that will allow me to do this easily or any samples that I can work through. I initially looked at the basic structure of DDI and there are a lot of elements to choose from for me to know whether I'm mapping things correctly or not. Kind Regards, Stein -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.icpsr.umich.edu/pipermail/ddi-users/attachments/20091118/87d343a2/attachment.html From wlt at pop.umn.edu Wed Nov 18 15:11:45 2009 From: wlt at pop.umn.edu (Wendy Thomas) Date: Wed, 18 Nov 2009 14:11:45 -0600 (CST) Subject: [DDI-users] [DDI-UOG-Chair] Adopting DDI for a survey In-Reply-To: <25C6BB73D3916546AD374E64735FC7080BF65BC5@EXPO12.exchange.mit.edu> References: <25C6BB73D3916546AD374E64735FC7080BF65BC5@EXPO12.exchange.mit.edu> Message-ID: Stein, I am assuming this may be part of the larger project ABS is undertaking. You may wish to talk to Alistair Hamilton at ABS as he is one of the people involved in setting up some addtional training etc within ABS on DDI. If you are focusing on variables you may wish to look at some of the SPSS and SAS to DDI 3 tools like DeXT and one by Achim Wackerow. These are on the ddi tools page http://tools.ddialliance.org/?lvl1=library This will let you see where elements you are familier with from statistical packages reside within a DDI instance. Coming from a questionnaire perspective I would suggest talking to the developers at Algenta (Jeremy Iverson ). While their tool is commercial they have a beta version you should be able to use and again create DDI output that will provide you with a better sense of how the content is arranged. If you have not already done so, download the schema package. It contains both an Overview and Users Guide which may be helpful. I don't know how helpful the current set of best practices will be http://www.ddialliance.org/DDI/bp/ as they don't tend to deal with this basic use case. If you have specific question, either post them to the list or directly to me. I chair the Technical Implimentation Committee and provide user support to DDI. Wendy Thomas On Wed, 18 Nov 2009, Katherine McNeill wrote: > Stein, > > Thank you for your interest, and I'm also forwarding your message to the DDI Users email list, where other users (many of whom I know have experience in Blaise) can respond to your question as well. There is a particular section of the DDI that would be use to document the variables (specifically in the logical product module: http://gandalf.opendatafoundation.org/infocenter/topic/net.sf.ddialliance.help/html/modules/ddi3_logicalproduct.html), whereas most of the other elements document other contextual information about the data (collection, storage formats, etc.). > > As for tools, there's a simple DDI editor tool at: http://www.ddialliance.org/DDI/ddi3/editor-lite-3/DDI_v2dot2.html > Within the DDI Tools project page (http://tools.ddialliance.org/?lvl1=library) you can view a list of XML examples, and the first one in the list shows examples of markup of variables. > > And I believe that others who respond to your question will be able to provide even more detailed guidance. > > Sincerely, > Katherine McNeill > > From: ddi-uog-chair-bounces at ddialliance.org [mailto:ddi-uog-chair-bounces at ddialliance.org] On Behalf Of Steinberg Tan > Sent: Tuesday, November 17, 2009 9:37 PM > To: ddi-uog-chair at icpsr.umich.edu > Cc: Steinberg Tan > Subject: [DDI-UOG-Chair] Adopting DDI for a survey > > Hi, > > My name's Steinberg and I work for the Australian Bureau of Statistics. I am currently involved in a pilot project to see if we can map a small survey to DDI standard. I've been reading some of the papers and presentations on the net but am still a bit confused about how we go about mapping it. > > Our current system (end-to-end system) consists of various components from our data store (star schema) to Blaise (edits and data entry) and many others in-between. For this pilot project, our initial goal is to map every variable in the survey form to DDI - I'm writing to ask if there are any tools that will allow me to do this easily or any samples that I can work through. I initially looked at the basic structure of DDI and there are a lot of elements to choose from for me to know whether I'm mapping things correctly or not. > > Kind Regards, > Stein > Wendy L. Thomas Phone: +1 612.624.4389 Data Access Core Director Fax: +1 612.626.8375 Minnesota Population Center Email: wlt at pop.umn.edu University of Minnesota 50 Willey Hall 225 19th Avenue South Minneapolis, MN 55455 From a.amin at uvt.nl Tue Nov 24 08:48:28 2009 From: a.amin at uvt.nl (Alerk Amin) Date: Tue, 24 Nov 2009 14:48:28 +0100 Subject: [DDI-users] language tags Message-ID: <4B0BE42C.5090306@uvt.nl> Hello, In looking at the DDI 3.1 specification, I have a question regarding language tags. This issue doesn't cause us problems today, but might in the future. As far as I know, the xml:lang attribute accepts IETF language tags (BCP 47 standard track). This consists of a language tag, with additional optional tags, including region and script. The script tag is important for us, because for one project, we have 2 translations into the same language/region, with 2 different scripts. As most DDI elements use the xml:lang attribute to specify the language, this is fine with us. However, the Language element from the ddi:instance:3_1 namespace does not specify what standard to use for the language. If I look at the Language element in the ddi:reusable:3_1 namespace, it specifies only a pair of codes for language and locale (ISO 3166 for country codes, and I assume ISO 639-1 for language). The LanguageOfData element only specifies "a 2-character ISO language code" (ISO 639-1?). The Language element in the ddi:archive:3_1 namespace does not specify which standard to use, but its type is xs:language, so I assume I can use IETF language tags, as with xml:lang. Is the above interpretation correct? If not, please let me know where I am mistaken. I think we would prefer to use IETF language tags everywhere. We will likely use the TranslationInformation element in the future, and will will need the ability to specify the script at that time. Thank you for your help. Best, Alerk -- Alerk Amin Senior Software Developer CentERdata Room K737 (Tilburg University, Koopmans Building) Postal address : PO Box 90153, 5000 LE Tilburg, The Netherlands Visiting address : Warandelaan 2, 5037 AB Tilburg, The Netherlands Telephone : +31-13-466 2243 / 8325 Fax : +31-13-466 2764 WWW : www.centerdata.nl Disclaimer : See http://www.centerdata.nl/maildisclaimer. From wlt at pop.umn.edu Tue Nov 24 09:54:38 2009 From: wlt at pop.umn.edu (Wendy Thomas) Date: Tue, 24 Nov 2009 08:54:38 -0600 (CST) Subject: [DDI-users] language tags In-Reply-To: <4B0BE42C.5090306@uvt.nl> References: <4B0BE42C.5090306@uvt.nl> Message-ID: Alerk, I did a preliminary scan through the schemas and found multiple means of capturing language at different points. There were related issues raised in the Expert Workshop relating to grouping and language. I am going to file this information under a bug and call for a systematic review of language elements and attributes with the goal of a consistant approach within DDI that will meet the needs you specified below as well as those raised in Expert Workshop. Wendy On Tue, 24 Nov 2009, Alerk Amin wrote: > Hello, > > In looking at the DDI 3.1 specification, I have a question regarding > language tags. This issue doesn't cause us problems today, but might in > the future. > As far as I know, the xml:lang attribute accepts IETF language tags > (BCP 47 standard track). This consists of a language tag, with > additional optional tags, including region and script. The script tag > is important for us, because for one project, we have 2 translations > into the same language/region, with 2 different scripts. As most DDI > elements use the xml:lang attribute to specify the language, this is > fine with us. > However, the Language element from the ddi:instance:3_1 namespace > does not specify what standard to use for the language. If I look at > the Language element in the ddi:reusable:3_1 namespace, it specifies > only a pair of codes for language and locale (ISO 3166 for country > codes, and I assume ISO 639-1 for language). The LanguageOfData element > only specifies "a 2-character ISO language code" (ISO 639-1?). The > Language element in the ddi:archive:3_1 namespace does not specify which > standard to use, but its type is xs:language, so I assume I can use IETF > language tags, as with xml:lang. > Is the above interpretation correct? If not, please let me know > where I am mistaken. > I think we would prefer to use IETF language tags everywhere. We > will likely use the TranslationInformation element in the future, and > will will need the ability to specify the script at that time. > Thank you for your help. > > Best, > Alerk > > -- > Alerk Amin > Senior Software Developer > CentERdata > Room K737 (Tilburg University, Koopmans Building) > Postal address : PO Box 90153, 5000 LE Tilburg, The Netherlands > Visiting address : Warandelaan 2, 5037 AB Tilburg, The Netherlands > Telephone : +31-13-466 2243 / 8325 > Fax : +31-13-466 2764 > WWW : www.centerdata.nl > Disclaimer : See http://www.centerdata.nl/maildisclaimer. > > _______________________________________________ > DDI-users mailing list > DDI-users at icpsr.umich.edu > http://www.icpsr.umich.edu/mailman/listinfo/ddi-users > Wendy L. Thomas Phone: +1 612.624.4389 Data Access Core Director Fax: +1 612.626.8375 Minnesota Population Center Email: wlt at pop.umn.edu University of Minnesota 50 Willey Hall 225 19th Avenue South Minneapolis, MN 55455 From joachim.wackerow at gesis.org Tue Nov 24 10:15:17 2009 From: joachim.wackerow at gesis.org (Joachim Wackerow) Date: Tue, 24 Nov 2009 16:15:17 +0100 Subject: [DDI-users] language tags In-Reply-To: References: <4B0BE42C.5090306@uvt.nl> Message-ID: <4B0BF885.7040603@gesis.org> Alerk, The intention of ALL language related elements/attributes in DDI3 is to use the values allowed as for xml:lang. Maybe this is not clear enough in the documentation and in the definition of these elements/attributes in the XML Schema. As Wendy said this should be reviewed. A quite instructive page about language tags in HTML and XML is available at W3C. This would also apply to the language values at several places in DDI3. The page describes the detailed structure of the tags when the ISO code isn't sufficient for the description of a language. http://www.w3.org/International/articles/language-tags/ The page mentioned above is basically a description of the content of the official RFC 4646. http://tools.ietf.org/html/rfc4646 The ISO three-letter codes should be used, when languages should be defined which have no two-letter code. When the ISO three-letter code is not sufficient, the Language Subtag Registry at IANA (Internet Assigned Numbers Authority) may help: http://www.iana.org/assignments/language-subtag-registry Search Tool by Richard Ishida: http://people.w3.org/rishida/utils/subtags/ Hope this helps Achim Wendy Thomas wrote: > Alerk, > > I did a preliminary scan through the schemas and found multiple means of > capturing language at different points. There were related issues raised > in the Expert Workshop relating to grouping and language. I am going to > file this information under a bug and call for a systematic review of > language elements and attributes with the goal of a consistant approach > within DDI that will meet the needs you specified below as well as those > raised in Expert Workshop. > > Wendy > > > On Tue, 24 Nov 2009, Alerk Amin wrote: > >> Hello, >> >> In looking at the DDI 3.1 specification, I have a question regarding >> language tags. This issue doesn't cause us problems today, but might in >> the future. >> As far as I know, the xml:lang attribute accepts IETF language tags >> (BCP 47 standard track). This consists of a language tag, with >> additional optional tags, including region and script. The script tag >> is important for us, because for one project, we have 2 translations >> into the same language/region, with 2 different scripts. As most DDI >> elements use the xml:lang attribute to specify the language, this is >> fine with us. >> However, the Language element from the ddi:instance:3_1 namespace >> does not specify what standard to use for the language. If I look at >> the Language element in the ddi:reusable:3_1 namespace, it specifies >> only a pair of codes for language and locale (ISO 3166 for country >> codes, and I assume ISO 639-1 for language). The LanguageOfData element >> only specifies "a 2-character ISO language code" (ISO 639-1?). The >> Language element in the ddi:archive:3_1 namespace does not specify which >> standard to use, but its type is xs:language, so I assume I can use IETF >> language tags, as with xml:lang. >> Is the above interpretation correct? If not, please let me know >> where I am mistaken. >> I think we would prefer to use IETF language tags everywhere. We >> will likely use the TranslationInformation element in the future, and >> will will need the ability to specify the script at that time. >> Thank you for your help. >> >> Best, >> Alerk >> >> -- >> Alerk Amin >> Senior Software Developer >> CentERdata >> Room K737 (Tilburg University, Koopmans Building) >> Postal address : PO Box 90153, 5000 LE Tilburg, The Netherlands >> Visiting address : Warandelaan 2, 5037 AB Tilburg, The Netherlands >> Telephone : +31-13-466 2243 / 8325 >> Fax : +31-13-466 2764 >> WWW : www.centerdata.nl >> Disclaimer : See http://www.centerdata.nl/maildisclaimer. >> >> _______________________________________________ >> DDI-users mailing list >> DDI-users at icpsr.umich.edu >> http://www.icpsr.umich.edu/mailman/listinfo/ddi-users >> > > Wendy L. Thomas Phone: +1 612.624.4389 > Data Access Core Director Fax: +1 612.626.8375 > Minnesota Population Center Email: wlt at pop.umn.edu > University of Minnesota > 50 Willey Hall > 225 19th Avenue South > Minneapolis, MN 55455 > _______________________________________________ > DDI-users mailing list > DDI-users at icpsr.umich.edu > http://www.icpsr.umich.edu/mailman/listinfo/ddi-users -- GESIS - Leibniz Institute for the Social Sciences Postal address: P.O. Box 122155, 68072 Mannheim, Germany Visiting address: B2 1, 68159 Mannheim, Germany Phone: +49 (0)621 1246 262 Fax: +49 (0)621 1246 100 E-mail: joachim.wackerow at gesis.org www.gesis.org/en/institute/ From wlt at pop.umn.edu Tue Nov 24 10:25:14 2009 From: wlt at pop.umn.edu (Wendy Thomas) Date: Tue, 24 Nov 2009 09:25:14 -0600 (CST) Subject: [DDI-users] language tags In-Reply-To: <4B0BF885.7040603@gesis.org> References: <4B0BE42C.5090306@uvt.nl> <4B0BF885.7040603@gesis.org> Message-ID: I've added this information to the bug contents. Its bug 315 by the way. Wendy On Tue, 24 Nov 2009, Joachim Wackerow wrote: > Alerk, > > The intention of ALL language related elements/attributes in DDI3 is to > use the values allowed as for xml:lang. Maybe this is not clear enough > in the documentation and in the definition of these elements/attributes > in the XML Schema. As Wendy said this should be reviewed. > > A quite instructive page about language tags in HTML and XML is > available at W3C. This would also apply to the language values at > several places in DDI3. The page describes the detailed structure of the > tags when the ISO code isn't sufficient for the description of a language. > http://www.w3.org/International/articles/language-tags/ > > The page mentioned above is basically a description of the content of > the official RFC 4646. > http://tools.ietf.org/html/rfc4646 > > The ISO three-letter codes should be used, when languages should be > defined which have no two-letter code. > > When the ISO three-letter code is not sufficient, the Language Subtag > Registry at IANA (Internet Assigned Numbers Authority) may help: > http://www.iana.org/assignments/language-subtag-registry > > Search Tool by Richard Ishida: > http://people.w3.org/rishida/utils/subtags/ > > Hope this helps > Achim > > Wendy Thomas wrote: >> Alerk, >> >> I did a preliminary scan through the schemas and found multiple means of >> capturing language at different points. There were related issues raised >> in the Expert Workshop relating to grouping and language. I am going to >> file this information under a bug and call for a systematic review of >> language elements and attributes with the goal of a consistant approach >> within DDI that will meet the needs you specified below as well as those >> raised in Expert Workshop. >> >> Wendy >> >> >> On Tue, 24 Nov 2009, Alerk Amin wrote: >> >>> Hello, >>> >>> In looking at the DDI 3.1 specification, I have a question regarding >>> language tags. This issue doesn't cause us problems today, but might in >>> the future. >>> As far as I know, the xml:lang attribute accepts IETF language tags >>> (BCP 47 standard track). This consists of a language tag, with >>> additional optional tags, including region and script. The script tag >>> is important for us, because for one project, we have 2 translations >>> into the same language/region, with 2 different scripts. As most DDI >>> elements use the xml:lang attribute to specify the language, this is >>> fine with us. >>> However, the Language element from the ddi:instance:3_1 namespace >>> does not specify what standard to use for the language. If I look at >>> the Language element in the ddi:reusable:3_1 namespace, it specifies >>> only a pair of codes for language and locale (ISO 3166 for country >>> codes, and I assume ISO 639-1 for language). The LanguageOfData element >>> only specifies "a 2-character ISO language code" (ISO 639-1?). The >>> Language element in the ddi:archive:3_1 namespace does not specify which >>> standard to use, but its type is xs:language, so I assume I can use IETF >>> language tags, as with xml:lang. >>> Is the above interpretation correct? If not, please let me know >>> where I am mistaken. >>> I think we would prefer to use IETF language tags everywhere. We >>> will likely use the TranslationInformation element in the future, and >>> will will need the ability to specify the script at that time. >>> Thank you for your help. >>> >>> Best, >>> Alerk >>> >>> -- >>> Alerk Amin >>> Senior Software Developer >>> CentERdata >>> Room K737 (Tilburg University, Koopmans Building) >>> Postal address : PO Box 90153, 5000 LE Tilburg, The Netherlands >>> Visiting address : Warandelaan 2, 5037 AB Tilburg, The Netherlands >>> Telephone : +31-13-466 2243 / 8325 >>> Fax : +31-13-466 2764 >>> WWW : www.centerdata.nl >>> Disclaimer : See http://www.centerdata.nl/maildisclaimer. >>> >>> _______________________________________________ >>> DDI-users mailing list >>> DDI-users at icpsr.umich.edu >>> http://www.icpsr.umich.edu/mailman/listinfo/ddi-users >>> >> >> Wendy L. Thomas Phone: +1 612.624.4389 >> Data Access Core Director Fax: +1 612.626.8375 >> Minnesota Population Center Email: wlt at pop.umn.edu >> University of Minnesota >> 50 Willey Hall >> 225 19th Avenue South >> Minneapolis, MN 55455 >> _______________________________________________ >> DDI-users mailing list >> DDI-users at icpsr.umich.edu >> http://www.icpsr.umich.edu/mailman/listinfo/ddi-users > > > -- > GESIS - Leibniz Institute for the Social Sciences > Postal address: P.O. Box 122155, 68072 Mannheim, Germany > Visiting address: B2 1, 68159 Mannheim, Germany > Phone: +49 (0)621 1246 262 > Fax: +49 (0)621 1246 100 > E-mail: joachim.wackerow at gesis.org > www.gesis.org/en/institute/ > _______________________________________________ > DDI-users mailing list > DDI-users at icpsr.umich.edu > http://www.icpsr.umich.edu/mailman/listinfo/ddi-users > Wendy L. Thomas Phone: +1 612.624.4389 Data Access Core Director Fax: +1 612.626.8375 Minnesota Population Center Email: wlt at pop.umn.edu University of Minnesota 50 Willey Hall 225 19th Avenue South Minneapolis, MN 55455