<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Gulim;
        panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
        {font-family:Gulim;
        panose-1:2 11 6 0 0 1 1 1 1 1;}
@font-face
        {font-family:"Malgun Gothic";
        panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"Malgun Gothic";
        panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
        {font-family:Gulim;
        panose-1:2 11 6 0 0 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:black;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
pre
        {mso-style-priority:99;
        mso-style-link:"\BBF8\B9AC \C11C\C2DD\C774 \C9C0\C815\B41C HTML Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";
        color:black;}
span.HTMLChar
        {mso-style-name:"\BBF8\B9AC \C11C\C2DD\C774 \C9C0\C815\B41C HTML Char";
        mso-style-priority:99;
        mso-style-link:"\BBF8\B9AC \C11C\C2DD\C774 \C9C0\C815\B41C HTML";
        font-family:"Courier New";
        color:black;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Malgun Gothic";
        color:#1F497D;}
..MsoChpDefault
        {mso-style-type:export-only;}
@page Section1
        {size:612.0pt 792.0pt;
        margin:3.0cm 72.0pt 72.0pt 72.0pt;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=KO link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span lang=EN-US>Subject-Object-Verb</span><span lang=EN-US>
order is just one issue, but not the major one. I don’t want get into
that argument here.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>I just wanted to point out that naturalness
in one culture may be awkwardness in other different culture.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US>That is why I advocate a kind of
culture-neutral notation with semicolon. <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US>If one desperately need it, and the other
can tolerate with it, well, IMHO, I would go with it.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>If you want an explanation of why it is
awkward, not just because of word order, please let me know.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US>I can give you a 5 min lecture :) <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Malgun Gothic";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:Gulim;
color:#1F497D'>---<br>
Jaeho Lee<br>
The University of Seoul<br>
</span><span lang=EN-US style='font-size:10.0pt;font-family:"Malgun Gothic";
color:#1F497D'><o:p></o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:windowtext'>From:</span></b><span lang=EN-US
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>
sc34wg3-bounces@isotopicmaps.org [mailto:sc34wg3-bounces@isotopicmaps.org] <b>On
Behalf Of </b>Xuan Baldauf<br>
<b>Sent:</b> Thursday, January 31, 2008 6:47 AM<br>
<b>To:</b> Discussion of ISO/IEC 13250 Topic Maps<br>
<b>Cc:</b> rho@devc.at<br>
<b>Subject:</b> Re: [sc34wg3] CTM: Realistic use cases or toy examples?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>Jaeho Lee wrote: <o:p></o:p></span></p>
<pre><span lang=EN-US>[...]<o:p></o:p></span></pre><pre><span lang=EN-US>If the topic maps on the left column in the comparison list are written, for<o:p></o:p></span></pre><pre><span
lang=EN-US>example in Korean, it would be really cryptic because it doesn't give enough<o:p></o:p></span></pre><pre><span
lang=EN-US>clue to distinguish between associations and topics.<o:p></o:p></span></pre><pre><span
lang=EN-US>To me and probably to people in other cultures, the left column is HORRIFIC<o:p></o:p></span></pre><pre><span
lang=EN-US>to read.<o:p></o:p></span></pre><pre><span lang=EN-US>Structural boundaries such as semi-colons are definitely needed for<o:p></o:p></span></pre><pre><span
lang=EN-US>readability, IMHO, even in English.<o:p></o:p></span></pre><pre><span
lang=EN-US> <o:p></o:p></span></pre>
<p class=MsoNormal><span lang=EN-US>I think your point of cultural bias
regarding what makes a language readable is quite valid. However, if
there is only one person telling some language instance is horrific to read, it
is indistinguishable from personal bias. ;-) So it would be nice if we could
gather input from more people with non-Germanic cultural background (i.e.
Japanese? Chinese? ).<br>
<br>
Nevertheless, do you think, in your own opinion, that some indentation-standard
(though not mandatory, but customary) like<o:p></o:p></span></p>
<pre><span lang=EN-US>john<o:p></o:p></span></pre><pre><span lang=EN-US> isa singer<o:p></o:p></span></pre><pre><span
lang=EN-US> isa guitarist .<o:p></o:p></span></pre>
<p class=MsoNormal><span lang=EN-US>provides enough structure?<br>
<br>
As Korean is mainly a Subject-Object-Verb-Language AFAIK, would<o:p></o:p></span></p>
<pre><span lang=EN-US>john<o:p></o:p></span></pre><pre><span lang=EN-US> singer isa<o:p></o:p></span></pre><pre><span
lang=EN-US> guitarist isa .<o:p></o:p></span></pre><pre><span lang=EN-US> <o:p></o:p></span></pre>
<p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US>look better?<br>
<br>
I'm asking this to find out whether it is possible at all to maximize CTM
usability while being as far as culture-neutral as possible, or whether there
exist multiple usability maximums, one for each culture, which compete against
each other in such a way that it would be more wise to just choose one of these
usability maximums, even if this means that culture-neutrality is grossly not
achieved. If culture-neutrality is not achievable (while achieving other good
CTM properties) in principle, there is not much point in argueing in favor of a
specific cultural POV, except when it comes to increasing some part of the CTM
userbase at cost of a smaller decrease at some other parts of the CTM userbase
(i.e. maybe we should have a lot of Chinese-like syntax if we expect a lot of
CTM authors being from a Chinese cultural background).<br>
<br>
<br>
ciao,<br>
Xuân.<o:p></o:p></span></p>
</div>
</body>
</html>