Received: from mail-ee0-f55.google.com ([74.125.83.55]:58918) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.80.1) (envelope-from ) id 1YLvPs-0007bF-7A for lojban-list-archive@lojban.org; Thu, 12 Feb 2015 07:11:11 -0800 Received: by mail-ee0-f55.google.com with SMTP id c13sf2674460eek.0 for ; Thu, 12 Feb 2015 07:10:49 -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=w54baygpLnCTLpuqk6LFIKr2IJfCzakDgtPQCpuffq0=; b=Nwnv4FZMK6RmSwTSBxITI4hvDnBdZDMcrRW2p9dQ+wfwXWGN+CETNgB6d/RG88g1f0 QDsbjTo3PGtriAJ4PbFqFkOOy9m6okjnbyxROccdPeqUqXxheFAALNMnYkbhUTsLbmz5 c3NTHqYEaK8KkMrtE1sqYcf2cNxiSjv2b5ldHx2RE2a8+71TzvkRec6/PJHhC/mPer/U d5iSFF4AE2Fn2uICJeN2K+HaeMJMJ8yDfvIIWnQ16wAw8xvrKJXOSmV28zqcv7IbbPGn XZDVIZHwHbg10B0te0LwfCSfALMpYu0qqocDrSN9Yh0jMbyZ4RzOS7fbir0agpiSpnUg YpHw== X-Received: by 10.180.98.40 with SMTP id ef8mr32993wib.10.1423753849452; Thu, 12 Feb 2015 07:10:49 -0800 (PST) X-BeenThere: lojban@googlegroups.com Received: by 10.180.95.232 with SMTP id dn8ls162438wib.15.canary; Thu, 12 Feb 2015 07:10:48 -0800 (PST) X-Received: by 10.194.161.194 with SMTP id xu2mr651281wjb.1.1423753848870; Thu, 12 Feb 2015 07:10:48 -0800 (PST) Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com. [2a00:1450:400c:c05::233]) by gmr-mx.google.com with ESMTPS id jx7si1930431wid.2.2015.02.12.07.10.48 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Feb 2015 07:10:48 -0800 (PST) Received-SPF: pass (google.com: domain of gleki.is.my.name@gmail.com designates 2a00:1450:400c:c05::233 as permitted sender) client-ip=2a00:1450:400c:c05::233; Received: by mail-wi0-x233.google.com with SMTP id hi2so5066539wib.0 for ; Thu, 12 Feb 2015 07:10:48 -0800 (PST) X-Received: by 10.194.122.38 with SMTP id lp6mr9235563wjb.24.1423753848718; Thu, 12 Feb 2015 07:10:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.86.200 with HTTP; Thu, 12 Feb 2015 07:10:27 -0800 (PST) In-Reply-To: <20150212150021.GB4686@kuebelreiter.informatik.Uni-Osnabrueck.DE> References: <20150204124517.GA1243@kuebelreiter.informatik.Uni-Osnabrueck.DE> <20150212123856.GA831@kuebelreiter.informatik.Uni-Osnabrueck.DE> <20150212150021.GB4686@kuebelreiter.informatik.Uni-Osnabrueck.DE> From: Gleki Arxokuna Date: Thu, 12 Feb 2015 18:10:27 +0300 Message-ID: Subject: Re: [lojban] the myth of monoparsing To: "lojban@googlegroups.com" Content-Type: multipart/alternative; boundary=089e01227ee4668c5b050ee58664 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:c05::233 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: -1.9 (-) X-Spam_score: -1.9 X-Spam_score_int: -18 X-Spam_bar: - --089e01227ee4668c5b050ee58664 Content-Type: text/plain; charset=UTF-8 2015-02-12 18:00 GMT+03:00 v4hn : > First off, learn to quote properly. > This whole thread (as well as a number of other threads > you were involved in) is a mess to read. > > On Thu, Feb 12, 2015 at 04:22:52PM +0300, Gleki Arxokuna wrote: > > 2015-02-12 15:38 GMT+03:00 v4hn : > > > So, in essence, you do not question monoparsing in lojban, > > > but instead propose a new theory on how to parse natural languages. > > > Why didn't you say so right away? > > > > May be because I did say it in the first sentence of the first post of > this > > thread? > > > Since the original post on monoparsing as something unique or defining > > feature of Lojban provided no examples on how this monoparsing differs > from > > English here is once again my full understanding using one example that > is > > monoparsed both in English and Lojban: > > You use your version of "monoparsing" here without explaining anything. > So, no, you did not. Whatever. > It's the same version. Monoparsing is having one syntactic tree as the result of the work of a parser. > > > My complaint is (ke'usai) [about] > > monoparsing as something unique or defining feature of > Lojban > > Ok, it seems to be of no relevance to you at all. > What seems not be of relevance to me? I disagree with a statement. > That's your opinion, so, for me and a number of others on this list, > it's just another "Someone is wrong on the internet". http://xkcd.com/386/ > I consider implemented and usable monoparsing to be > one of the most important features of lojban. > No, not Lojban but its parsers. Please, differentiate between languages and tools to analyze them. > > > This is like comparing sweet with red. If both parsers could be aligned > we > > would see monoparsing (or polyparsing) in both languages. > > [...] > > It seems to me that monoparsing is not a defining feature of Lojban and > in > > fact it's quite natural for most languages to be monoparsed in most cases > > That's untying knots with a sword. > "Every sentence (regardless the language) monoparses > because all of its ambiguity is hidden in its structure." > helps no one, but sure, you can go there. > > For me, the crutial difference between your {poi vofli} sentence and > the English "flying" sentence is that you need a zero-morpheme to > "gleki-monoparse" > the latter one, English parsers inject zero-morphemes all the time to avoid problems. I don't see why this can't be done this time. > where the first one moves the structure ambiguity > to a semantic level. Your argumentation here pe'i seems analogous to > saying that > "Fred saw a plane while he flew over Zurich or he saw a plane that flew > over Zurich" > is the same as "Fred saw a plane flying over Zurich". > This is not the case w.r.t. parsing. W.r.t. utterance analysis they are > also quite > different, as Grice tells us that if somebody spends so many words on > making > the uncertainty in this sentence explicit (instead of identifying one > interpretation), > either the uncertainty is quite important or the speaker is a linguist... > Not all languages show ambiguity in this example. Thus no language can be concise in showing syntactic vagueness. And that's why English is unlucky that its structure is expressed using {se xi vei mo'e zo'e} which you may consider breaking Gricean principles. One can imagine a shortcut for this {se xi vei mo'e zo'e} but we differentiate between parsing (which requires adding new words to show the sturucture of a sentence) and live Lojban that isn't going to imitate any natlangs. > > No example has been shown of how can monoparsing be never reached in > > natlangs if compared to how Lojban parses them. > > I can't even parse that sentence properly, so I'm not sure what kind of > "example" you want as proof that something cannot be done. > Which sentence? With Fred? You can't or English parser can't? > > No wonder that such myths are spread without any corroboration from real > > English and Lojban grammars and examples. > > You can call everything a myth, > but when it punches you in your stomach, > it will still hurt. > If a person utters claims without proofs then yes, it hurts. > > > I'm replying to the idea of monoparsing: > > "monoparsing is the essential Lojban virtue." > > [ http://pckipo.blogspot.ru/2014/06/lojban-is-monoparsing.html ] > > > > As I showed it is not an essential Lojban virtue. > > You didn't. It's your opinion. > > > It's an essential feature (not even virtue) of current Lojban parsers, > > although this may change in future [...] > > Everything you proposed in this thread to make lojban "polyparse" > is about semantic analysis, not about parsing. > Adding polyparsing to Lojban is possible by removing some parts of its grammar and it has nothing to do with semantic analysis. > > Last message from me in this thread, > > > v4hn > > -- > 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. --089e01227ee4668c5b050ee58664 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


2015-02-12 18:00 GMT+03:00 v4hn <me@v4hn.de>:
First off, learn to quote properly.
This whole thread (as well as a number of other threads
you were involved in) is a mess to read.

On Thu, Feb 12, 2015 at 04:22:52PM +0300, Gleki Arxokuna wrote:
> 2015-02-12 15:38 GMT+03:00 v4hn <me@v= 4hn.de>:
> > So, in essence, you do not question monop= arsing in lojban,
> > but instead propose a new theory on how to parse natural language= s.
> > Why didn't you say so right away?
>
> May be because I did say it in the first sentence of the first post of= this
> thread?

> Since the original post on monoparsing as some= thing unique or defining
> feature of Lojban provided no examples on how this monoparsing differs= from
> English here is once again my full understanding using one example tha= t is
> monoparsed both in English and Lojban:

You use your version of "monoparsing" here without explain= ing anything.
So, no, you did not. Whatever.

It's= the same version. Monoparsing is having one syntactic tree as the result o= f the work of a parser.

> My complaint is (ke'usai) [about]
> <quote>monoparsing as something unique or defin= ing feature of Lojban</quote>

Ok, it seems to be of no relevance to you at all.

What seems not be of relevance to me? I disagree with a s= tatement.
=C2=A0
That's your opinion, so, for me and a number of others on this list, it's just another "Someone is wrong on the internet". http://xkcd.com/386/
I consider implemented and usable monoparsing to be
one of the most important features of lojban.

No, not Lojban but its parsers.
Please, differentiate betw= een languages and tools to analyze them.
=C2=A0

> This is like comparing sweet with red. If both parsers could be aligne= d we
> would see monoparsing (or polyparsing) in both languages.
> [...]
> It seems to me that monoparsing is not a defining fea= ture of Lojban and in
> fact it's quite natural for most languages to be monoparsed in mos= t cases

That's untying knots with a sword.
"Every sentence (regardless the language) monoparses
because all of its ambiguity is hidden in its structure."
helps no one, but sure, you can go there.

For me, the crutial difference between your {poi vofli} sentence and
the English "flying" sentence is that you need a zero-morpheme to= "gleki-monoparse"
the latter one,

English parsers inject zero= -morphemes all the time to avoid problems.
I don't see why th= is can't be done this time.

=C2=A0
where the first one moves the structure ambiguity=
to a semantic level. Your argumentation here pe'i seems analogous to sa= ying that
"Fred saw a plane while he flew over Zurich or he saw a plane that fle= w over Zurich"
is the same as "Fred saw a plane flying over Zurich".
This is not the case w.r.t. parsing. W.r.t. utterance analysis they are als= o quite
different, as Grice tells us that if somebody spends so many words on makin= g
the uncertainty in this sentence explicit (instead of identifying one inter= pretation),
either the uncertainty is quite important or the speaker is a linguist...

Not all languages show ambiguity in this= example.
Thus no language can be concise in showing syntactic va= gueness.
And that's why English is unlucky that its structure= is expressed using {se xi vei mo'e zo'e} which you may consider br= eaking Gricean principles.

One can imagine a short= cut for this {se xi vei mo'e zo'e} but we differentiate between par= sing (which requires adding new words to show the sturucture of a sentence)= and live Lojban that isn't going to imitate any natlangs.


> No example has been shown of how can monoparsing be never reached in > natlangs if compared to how Lojban parses them.

I can't even parse that sentence properly, so I'm not sure w= hat kind of
"example" you want as proof that something cannot be done.

Which sentence? With Fred? You can't or E= nglish parser can't?


> No wonder that such myths are spread without any corroboration from re= al
> English and Lojban grammars and examples.

You can call everything a myth,
but when it punches you in your stomach,
it will still hurt.

If a person utters = claims without proofs then yes, it hurts.
=C2=A0

> I'm replying to the idea of monoparsing:
> "monoparsing is the essential Lojban virtue."
> [ http://pckipo.blogspot.ru/2014/06/lojban-is-monopars= ing.html ]
>
> As I showed it is not an essential Lojban virtue.

You didn't. It's your opinion.

> It's an essential feature (not even virtue) of current Lojban pars= ers,
> although this may change in future [...]

Everything you proposed in this thread to make lojban "polyparse"=
is about semantic analysis, not about parsing.

Adding polyparsing to Lojban is possible by removing some parts of = its grammar and it has nothing to do with semantic analysis.
=C2= =A0

Last message from me in this thread,


v4hn

--
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+uns= ubscribe@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.
--089e01227ee4668c5b050ee58664--