Received: from mail-wi0-f183.google.com ([209.85.212.183]:59018) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.80.1) (envelope-from ) id 1YJhro-0002MD-TI for lojban-list-archive@lojban.org; Fri, 06 Feb 2015 04:18:38 -0800 Received: by mail-wi0-f183.google.com with SMTP id bs8sf340986wib.0 for ; Fri, 06 Feb 2015 04:18:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-original-sender:x-original-authentication-results :reply-to:precedence:mailing-list:list-id:list-post:list-help :list-archive:sender:list-subscribe:list-unsubscribe; bh=xPri5bNfEH67RL/t6D4LUz7h+ehIkmiZA0dLxuTLekM=; b=P6RqMhxhXX7OFK9SljUHl0+l2j55yB5mKisKmCaqqIKTqeEECwDcDw5Xcvk9gTkBxC Yb9ez8rAK55a5w5bE4vt/3tsMbHU6JAFevMM3QgT+UAiCJKkjPEodwp2NLyFluslO+ri RWVAr/aS4XbW8M2KeCans3DtzgvBz6DTCgT7eOASOw9QGijDKFzDk+DeA8cDN32rEfLY aRzW2dK2/wK+UtkVORxymr8ZmODAZKLXwONY40lP5nMd8NyCnUyLtDIpakdnbL5VubMP lIwT6dDoXe+GI0IjmvHCN+8g5dbOVHXapf19KcPoL+hk8Z4g/gXrzcRFO5mUnJxmW0N+ EMUw== X-Received: by 10.152.88.115 with SMTP id bf19mr25171lab.15.1423225110186; Fri, 06 Feb 2015 04:18:30 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.152.3.130 with SMTP id c2ls253028lac.77.gmail; Fri, 06 Feb 2015 04:18:29 -0800 (PST) X-Received: by 10.112.35.135 with SMTP id h7mr406573lbj.23.1423225109296; Fri, 06 Feb 2015 04:18:29 -0800 (PST) Received: from mail-we0-x241.google.com (mail-we0-x241.google.com. [2a00:1450:400c:c03::241]) by gmr-mx.google.com with ESMTPS id ev8si74907wib.3.2015.02.06.04.18.29 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Feb 2015 04:18:29 -0800 (PST) Received-SPF: pass (google.com: domain of gleki.is.my.name@gmail.com designates 2a00:1450:400c:c03::241 as permitted sender) client-ip=2a00:1450:400c:c03::241; Received: by mail-we0-f193.google.com with SMTP id k11so3171061wes.0 for ; Fri, 06 Feb 2015 04:18:29 -0800 (PST) X-Received: by 10.180.210.234 with SMTP id mx10mr2704467wic.37.1423225109134; Fri, 06 Feb 2015 04:18:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.86.200 with HTTP; Fri, 6 Feb 2015 04:18:08 -0800 (PST) In-Reply-To: References: From: Gleki Arxokuna Date: Fri, 6 Feb 2015 15:18:08 +0300 Message-ID: Subject: Re: [lojban] the myth of monoparsing To: "lojban@googlegroups.com" Content-Type: multipart/alternative; boundary=001a11c38d2010c19d050e6a6bf7 X-Original-Sender: gleki.is.my.name@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of gleki.is.my.name@gmail.com designates 2a00:1450:400c:c03::241 as permitted sender) smtp.mail=gleki.is.my.name@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: 0.8 (/) X-Spam_score: 0.8 X-Spam_score_int: 8 X-Spam_bar: / X-Spam-Report: Spam detection software, running on the system "stodi.digitalkingdom.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: 2015-02-06 15:01 GMT+03:00 And Rosta : > > On 6 Feb 2015 11:24, "Gleki Arxokuna" > >> > "Lojban is one of the few languages (along with e.g. gua\spi) that > has such interesting syntactic parsers that they perceive some sentences as > syntactically vague whereas as of 2015 most English parsers perceive them > as syntactically ambiguous. However, the humanity hopes that in future even > English parsers will reach the level Lojban has now". > >> > >> I recognize that that is your view. To me it currently seems as though > you don't understand what syntax is, given that you think there is such a > thing as "syntactic vagueness". > > > > > > oh, sorry. Let me try to clarify. > > I mean that there are several clauses floating in space and to which > haeds they are attached is not known. > > From the point of view of the parser, this is true. The possible > attachments licenced by the grammar are known, but the parser must choose > among them (which is disambiguation). > [...] Content analysis details: (0.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: googlegroups.com] 2.7 DNS_FROM_AHBL_RHSBL RBL: Envelope sender listed in dnsbl.ahbl.org [listed in googlegroups.com.rhsbl.ahbl.org. IN] [A] -0.0 RCVD_IN_MSPIKE_H3 RBL: Good reputation (+3) [209.85.212.183 listed in wl.mailspike.net] 0.0 T_HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail domains are different -0.0 SPF_PASS SPF: sender matches SPF record 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gleki.is.my.name[at]gmail.com) 0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is CUSTOM_MED 0.0 HTML_MESSAGE BODY: HTML included in message -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid 0.0 T_FREEMAIL_FORGED_FROMDOMAIN 2nd level domains in From and EnvelopeFrom freemail headers are different -0.0 RCVD_IN_MSPIKE_WL Mailspike good senders --001a11c38d2010c19d050e6a6bf7 Content-Type: text/plain; charset=UTF-8 2015-02-06 15:01 GMT+03:00 And Rosta : > > On 6 Feb 2015 11:24, "Gleki Arxokuna" > >> > "Lojban is one of the few languages (along with e.g. gua\spi) that > has such interesting syntactic parsers that they perceive some sentences as > syntactically vague whereas as of 2015 most English parsers perceive them > as syntactically ambiguous. However, the humanity hopes that in future even > English parsers will reach the level Lojban has now". > >> > >> I recognize that that is your view. To me it currently seems as though > you don't understand what syntax is, given that you think there is such a > thing as "syntactic vagueness". > > > > > > oh, sorry. Let me try to clarify. > > I mean that there are several clauses floating in space and to which > haeds they are attached is not known. > > From the point of view of the parser, this is true. The possible > attachments licenced by the grammar are known, but the parser must choose > among them (which is disambiguation). > The parser must choose???? But then this is a very critical limitation of the parser? Since when parsers HAVE TO attach to heads that aren't vague or can be derived from context? If an English parser used an analog to {zo'e} as some zero morpheme then a lot of (may be all but nobody knows) allegedly ambiguous sentences would become vague. If the theory of strictly applying relative clause to head of exact numbers isn't sufficient then a new theory that allows attaching to head No. {mo'e zo'e} has to be developed. Similarly, if you disallow parsing {se xi vei mo'e zo'e nei} then one could devise a workaround that would split such sentences into several like it currently happens to parsers of natlangs. It seems that Lojbanists created a parser and a language that is too powerful to be easily adopted to parsing natlangs. (Which is probably to the lack of information about Lojban in the world but that's another story). > So if you call this syntactic vagueness and everybody else calls it > syntactic ambiguity, let us agree to tolerate your terminological > eccentricity. > > > This is what happens both in the English and in the Lojban examples. > > It could be that that is what happens with Lojban -- since no explicit > grammar of Lojban exists, we can't say for sure -- but Lojban's design > principles are committed to the principle of no syntactic ambiguity (which, > following John Clifford, we call 'monoparsing'), and if that principle is > respected then the Lojban example does not work in the way the English one > does. > Then this is a useless term that only states that parsers for other languages lag behind in their development. > > > When you apply standard ways of dealing with the English sentence you > get syntactical ambiguity. > > Yes. > > > When you apply Lojban parsers you get monoparsing. > > Yes. > > > > >> Or, let me phrase that more charitably: your understanding of the > notion "syntax" appears to differ from other lojbanists' and > linguisticians'. I think you might be calling "syntax" not the encoded > logicosyntactic form but the enriched "logical explicature" derived from > the encoded logicosyntactic form, which is a complete proposition. A single > logicosyntactic form might, due to underspecification of logical relations, > be interpreted as any of many logical explicatures, and in such a case you > could call the sentence "logically vague". The monoparsing claim is that > every sentential phonological form corresponds to no more than one > logicosyntactic form, not that the logicosyntactic form it corresponds to > can be interpreted as no more than one logical explicature. > > > > Yes, and this is how I view the English sentence in question. > > Most English sentences are probably logically vague in some way, but the > standard view is that the English Zurich sentence is syntactically > ambiguous. > I'm fine with that! Then this is yet another useless term whereas "logicosyntactic form" is potentially a USEFUL term. You know that that's the standard view, of course. I don't mean to try to > crush you with an argument from authority, but pretty much every expert on > English would consider the Zurich sentence syntactically ambiguous. > But they can't compare to Lojban. May be they don't realize of find not illuminating adding a zero morpheme similar to {zo'e} that allows for {se xi vei mo'e zo'e GOhA}. And while the mere weight of authority alone should not suffice to make you > change your opinion, at least you'll understand why you're unable to > persuade anybody else that monoparsing is a myth. > > > > >> To avoid misunderstanding: I recognize that Lojban syntax doesn't exist > in any formal or explicit form, and that the claim that it is unambiguous > is based simply on the design principle that no ambiguity is permitted and > hence any syntax that allows ambiguity must be incorrect. > > > > It can't even be shown how Lojban syntax could be ambiguous. > > > > It is just explained in such a way that the question of polyparsing > never raises. > > It's all a matter of different terminology. > > The same standards, terminology and analytical framework are being applied > to both languages. > > For the Zurich sentence, there are no rules of English that say "this > phonological form can correspond to any of these n logicosyntactic forms". > Haven't you assumed that the logicosyntactical form can be only one, not several of them? It's accidental that the rules for assigning phonological forms to > logicosyntactic forms happen to assign certain logicosyntactic forms the > same phonological form. For your Lojban example, the conjectural rules of > logicosyntax generate this single logically vague form, and assign it a > phonological form that corresponds to no other logicosyntactic form. > You are starting from theory. But note that both sentences produce the same interpretation, the same 4 possible interpretations. If this happens then it might be that either the problem is in terminology and/or in theory that is unable to find the same structure in both sentences. Of course one sentence isn't enough but I can try translating other examples e.g. for one type of syntactic tree to avoid delving into numerous issues. --And. > > -- > You received this message because you are subscribed to the Google Groups > "lojban" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to lojban+unsubscribe@googlegroups.com. > To post to this group, send email to lojban@googlegroups.com. > Visit this group at http://groups.google.com/group/lojban. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "lojban" group. To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com. To post to this group, send email to lojban@googlegroups.com. Visit this group at http://groups.google.com/group/lojban. For more options, visit https://groups.google.com/d/optout. --001a11c38d2010c19d050e6a6bf7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


2015-02-06 15:01 GMT+03:00 And Rosta <and.rosta@gmail.com>:


On 6 Feb 2015 11:24, "Gleki Arxokuna"
>> > "Lojban is one of the few languages (along with e.g. gua= \spi) that has such interesting syntactic parsers that they perceive some s= entences as syntactically vague whereas as of 2015 most English parsers per= ceive them as syntactically ambiguous. However, the humanity hopes that in = future even English parsers will reach the level Lojban has now".
>>
>> I recognize that that is your view. To me it currently seems as th= ough you don't understand what syntax is, given that you think there is= such a thing as "syntactic vagueness".
>
>
> oh, sorry. Let me try to clarify.
> I mean that there are several clauses floating in space and to which h= aeds they are attached is not known.

From the point of view of the parser, this is true. The poss= ible attachments licenced by the grammar are known, but the parser must cho= ose among them (which is disambiguation).


The parser must choose???? But then this is a very critical limitation o= f the parser?
Since when parsers HAVE TO attach to heads that are= n't vague or can be derived from context?
If an English parse= r used an analog to {zo'e} as some zero morpheme then a lot of (may be = all but nobody knows) allegedly ambiguous sentences would become vague.

If the theory of strictly applying relative clause to= head of exact numbers isn't sufficient then a new theory that allows a= ttaching to head =C2=A0No. {mo'e zo'e} has to be developed.

Similarly, if you disallow parsing {se xi vei mo'e zo= 'e nei} then one could devise a workaround that would split such senten= ces into several like it currently happens to parsers of natlangs.

It seems that Lojbanists created a parser and a language t= hat is too powerful to be easily adopted to parsing natlangs. (Which is pro= bably to the lack of information about Lojban in the world but that's a= nother story).

So if you call this sy= ntactic vagueness and everybody else calls it syntactic ambiguity, let us a= gree to tolerate your terminological eccentricity.

> This is what happens both in the English and in the Loj= ban examples.

It could be that that is what happens with Lojban -- = since no explicit grammar of Lojban exists, we can't say for sure -- bu= t Lojban's design principles are committed to the principle of no synta= ctic ambiguity (which, following John Clifford, we call 'monoparsing= 9;), and if that principle is respected then the Lojban example does not wo= rk in the way the English one does.


The= n this is a useless term that only states that parsers for other languages = lag behind in their development.

>
> When you apply standard ways of dealing with the English sentence you = get syntactical ambiguity.

Yes.

> When you apply Lojban parsers you get =C2=A0monoparsing= .

Yes.

>
>> Or, let me phrase that more charitably: your understanding of the = notion "syntax" appears to differ from other lojbanists' and = linguisticians'. I think you might be calling "syntax" not th= e encoded logicosyntactic form but the enriched "logical explicature&q= uot; derived from the encoded logicosyntactic form, which is a complete pro= position. A single logicosyntactic form might, due to underspecification of= logical relations, be interpreted as any of many logical explicatures, and= in such a case you could call the sentence "logically vague". Th= e monoparsing claim is that every sentential phonological form corresponds = to no more than one logicosyntactic form, not that the logicosyntactic form= it corresponds to can be interpreted as no more than one logical explicatu= re.
>
> Yes, and this is how I view the English sentence in question.

Most English sentences are probably logically vague i= n some way, but the standard view is that the English Zurich sentence is sy= ntactically ambiguous.


I'm fine wit= h that! Then this is yet another useless term whereas=C2=A0
"= ;logicosyntactic form" is potentially a USEFUL term.

You know that that's the standa= rd view, of course. I don't mean to try to crush you with an argument f= rom authority, but pretty much every expert on English would consider the Z= urich sentence syntactically ambiguous.


But they can't compare to Lojban. May be they don't realize of fi= nd not illuminating adding a zero morpheme similar to {zo'e} that allow= s for {se xi vei mo'e zo'e GOhA}.

And while the mere weight of authority alone should not = suffice to make you change your opinion, at least you'll understand why= you're unable to persuade anybody else that monoparsing is a myth.

=

>
>> To avoid misunderstanding: I recognize that Lojban syntax doesn= 9;t exist in any formal or explicit form, and that the claim that it is una= mbiguous is based simply on the design principle that no ambiguity is permi= tted and hence any syntax that allows ambiguity must be incorrect.
>
> It can't even be shown how Lojban syntax could be ambiguous.=C2=A0=
>
> It is just explained in such a way that the question of polyparsing ne= ver raises.
> It's all a matter of different terminology.

The same standards, terminology and analytical framew= ork are being applied to both languages.

For the Zurich sentence, there are no rules of English that = say "this phonological form can correspond to any of these n logicosyn= tactic forms".


Haven't you ass= umed =C2=A0that the logicosyntactical form can be only one, not several of = them?

It's acciden= tal that the rules for assigning phonological forms to logicosyntactic form= s happen to assign certain logicosyntactic forms the same phonological form= . For your=C2=A0 Lojban example, the conjectural rules of logicosyntax gene= rate this single logically vague form, and assign it a phonological form th= at corresponds to no other logicosyntactic form.

You a= re starting from theory. But note that both sentences produce the same inte= rpretation, the same 4 possible interpretations.

I= f this happens then it might be that either the problem is in terminology a= nd/or in theory that is unable to find the same structure in both sentences= .

Of course one sentence isn't enough but I ca= n try translating other examples e.g. for one type of syntactic tree to avo= id delving into numerous issues.

--And.

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsub= scribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http:= //groups.google.com/group/lojban.
For more options, visit http= s://groups.google.com/d/optout.
--001a11c38d2010c19d050e6a6bf7--