Received: from mail-qc0-f189.google.com ([209.85.216.189]:48918) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1SpRaD-0004dH-CK; Thu, 12 Jul 2012 15:10:16 -0700 Received: by qcac11 with SMTP id c11sf3032412qca.16 for ; Thu, 12 Jul 2012 15:09:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:sender:in-reply-to:references :from:date:message-id:subject:to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive :list-subscribe:list-unsubscribe:content-type; bh=CIMsytoaAEKXipC0AO28auz0JE+I8HtiHPvK9i8+wSk=; b=xStjGeqUk3d74Zc/lHzyqzk66N8Vs/UNqhnEjJ+B4CCbtsAp0T/NiPUJJumIDPLW4b +09C0JeWJxYSo4c0fZqgOlHySh9yL6zysprCc15D9QeTUAKQUfWDJhIU7RAgyGrzf5i2 o0hwpWMFTUPXeExeLU5u1ro09DbO2y71PzzY0= Received: by 10.52.19.110 with SMTP id d14mr208vde.10.1342130994612; Thu, 12 Jul 2012 15:09:54 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.52.179.69 with SMTP id de5ls1458542vdc.1.gmail; Thu, 12 Jul 2012 15:09:54 -0700 (PDT) Received: by 10.52.33.1 with SMTP id n1mr10788vdi.4.1342130994046; Thu, 12 Jul 2012 15:09:54 -0700 (PDT) Received: by 10.52.33.1 with SMTP id n1mr10787vdi.4.1342130994023; Thu, 12 Jul 2012 15:09:54 -0700 (PDT) Received: from mail-vc0-f180.google.com (mail-vc0-f180.google.com [209.85.220.180]) by gmr-mx.google.com with ESMTPS id l12si275982vdf.3.2012.07.12.15.09.53 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 Jul 2012 15:09:54 -0700 (PDT) Received-SPF: pass (google.com: domain of rpglover64@gmail.com designates 209.85.220.180 as permitted sender) client-ip=209.85.220.180; Received: by vcbfk26 with SMTP id fk26so1723154vcb.25 for ; Thu, 12 Jul 2012 15:09:53 -0700 (PDT) Received: by 10.52.98.101 with SMTP id eh5mr12203vdb.8.1342130993793; Thu, 12 Jul 2012 15:09:53 -0700 (PDT) MIME-Version: 1.0 Sender: lojban@googlegroups.com Received: by 10.58.171.7 with HTTP; Thu, 12 Jul 2012 15:09:32 -0700 (PDT) In-Reply-To: <4FFF180C.8060000@gmail.com> References: <90a7e54c-42fe-4ee0-9693-8155db9a7646@googlegroups.com> <4FFDC7C8.2010707@gmail.com> <237c4ac5-64f3-40fa-81d3-8a97c76dcc5d@googlegroups.com> <1342109844.79789.YahooMailNeo@web184407.mail.bf1.yahoo.com> <4FFF180C.8060000@gmail.com> From: ".arpis." Date: Thu, 12 Jul 2012 18:09:32 -0400 Message-ID: Subject: Re: [lojban] &Lang To: lojban@googlegroups.com X-Original-Sender: rpglover64@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of rpglover64@gmail.com designates 209.85.220.180 as permitted sender) smtp.mail=rpglover64@gmail.com; dkim=pass header.i=@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-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=20cf307f34e4208c5604c4a939fd X-Spam-Score: 0.0 (/) X-Spam_score: 0.0 X-Spam_score_int: 0 X-Spam_bar: / --20cf307f34e4208c5604c4a939fd Content-Type: text/plain; charset=ISO-8859-1 The common way (speaking as a computer scientist) of avoiding variable repetition (and variable naming issues) in formal methods is to use De Bruijn indices (https://en.wikipedia.org/wiki/De_Bruijn_index), but this fails the requirement of fitting in human memory. On Thu, Jul 12, 2012 at 2:31 PM, And Rosta wrote: > Let me try harder to explain: > > > Take a variety of predicate logic consisting of predicates, quantifiers > and variables. In normal predicate logic notation, if a given variable is > an argument of more than one predicate, it gets repeated. And every bound > variable is notated at least twice, once where it is shown bound by > quantifier and once where it is argument of a predicate. But this is one > and the same variable; the repetition is a mere notational device necessary > to linearize the string. > > If the notation could be two dimensional, then you wouldn't need to write > variables at all. For simplicity's sake, I'll describe a notation for only > predicates and variables: > Use a 2 dimensional grid, infinite in both dimensions. > Each 'row' corresponds to a variable. > Each 'column' corresponds to a predicate. > Predicates are notated by sets of symbols, one symbol for each argument > place. Each argument place symbol is placed on the appropriate row for the > variable that fills the argument place. > > That's the basic data structure for predicate--argument structure. A > 2-dimensional notation can notate it without redundancy. But spoken > language is 1-dimensional. Is there a way of linearizing predicate-argument > structure ergonomically, in such a way that it is not so verbose or so > taxing on the memory that the advantages of its logical explicitness and > unambiguousness are not outweighed? > > --And. > > John E Clifford, On 12/07/2012 17:17: > >> As far as I can figure from the limited information, &'s language differs >> from Logjam in two significant respects. >> 1. Instead of a predicate with various arguments dripping from it, the >> core utterance is an argument (topic, say) with dangling predicates >> (comments -- not the standard usage quite but Logjam is not famous for >> following precedents in terminology). This is a feasible structure, easily >> realized in two (and simply in three) dimensions, without anaphora. The >> case of existential graphs and general topological considerations, however, >> suggest that anaphora will be needed in one-dimensional speech. The usual >> problems with that are simplified by the canonical location of topics. >> Multiple topics increase the complexity of this but not its basic >> simplicity. Comments come and go (naturally) while topics run on and on >> (and so are always available for connection). >> 2. Comments have no inherent places, which need to be filled implicitly >> when not explicitly, but have only those which are explicitly filled. This >> means, apparently, that the nature of the connection of a comment to its >> topic has to be specified in (almost) every case, an added nuisance in >> speech but probably a simplification in learning (and possible a reduction >> in the need for compounds, many of which are just to add a place to an >> existing predicate or rearrange those places). The bareness of comments >> means that comment words can be raised to topics directly to do business as >> properties or events, without a lot of extra detail. >> These points are too sketchy to give any notion of the relative size, >> ease or clarity of an &lang as here conceived, but at least it looks >> feasible so far. >> ** >> >> -- >> You received this message because you are subscribed to the Google Groups >> "lojban" group. >> To post to this group, send email to lojban@googlegroups.com. >> To unsubscribe from this group, send email to lojban+unsubscribe@** >> googlegroups.com . >> For more options, visit this group at http://groups.google.com/** >> group/lojban?hl=en . >> > > -- > You received this message because you are subscribed to the Google Groups > "lojban" group. > To post to this group, send email to lojban@googlegroups.com. > To unsubscribe from this group, send email to lojban+unsubscribe@** > googlegroups.com . > For more options, visit this group at http://groups.google.com/** > group/lojban?hl=en . > > -- mu'o mi'e .arpis. -- You received this message because you are subscribed to the Google Groups "lojban" group. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en. --20cf307f34e4208c5604c4a939fd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The common way (speaking as a computer scientist) of avoiding variable repe= tition (and variable naming issues) in formal methods is to use De Bruijn i= ndices (https://e= n.wikipedia.org/wiki/De_Bruijn_index), but this fails the requirement o= f fitting in human memory.

On Thu, Jul 12, 2012 at 2:31 PM, And Rosta <= span dir=3D"ltr"><and.rosta@gmail.com> wrote:
Let me try harder to explain:


Take a variety of predicate logic consisting of predicates, quantifiers and= variables. In normal predicate logic notation, if a given variable is an a= rgument of more than one predicate, it gets repeated. And every bound varia= ble is notated at least twice, once where it is shown bound by quantifier a= nd once where it is argument of a predicate. But this is one and the same v= ariable; the repetition is a mere notational device necessary to linearize = the string.

If the notation could be two dimensional, then you wouldn't need to wri= te variables at all. For simplicity's sake, I'll describe a notatio= n for only predicates and variables:
Use a 2 dimensional grid, infinite in both dimensions.
Each 'row' corresponds to a variable.
Each 'column' corresponds to a predicate.
Predicates are notated by sets of symbols, one symbol for each argument pla= ce. Each argument place symbol is placed on the appropriate row for the var= iable that fills the argument place.

That's the basic data structure for predicate--argument structure. A 2-= dimensional notation can notate it without redundancy. But spoken language = is 1-dimensional. Is there a way of linearizing predicate-argument structur= e ergonomically, in such a way that it is not so verbose or so taxing on th= e memory that the advantages of its logical explicitness and unambiguousnes= s are not outweighed?

--And.

John E Clifford, On 12/07/2012 17:17:
As far as I can figure from the limited information, &'s language d= iffers from Logjam in two significant respects.
1. Instead of a predicate with various arguments dripping from it, the core= utterance is an argument (topic, say) with dangling predicates (comments -= - not the standard usage quite but Logjam is not famous for following prece= dents in terminology). This is a feasible structure, easily realized in two= (and simply in three) dimensions, without anaphora. The case of existentia= l graphs and general topological considerations, however, suggest that anap= hora will be needed in one-dimensional speech. The usual problems with that= are simplified by the canonical location of topics. Multiple topics increa= se the complexity of this but not its basic simplicity. Comments come and g= o (naturally) while topics run on and on (and so are always available for c= onnection).
2. Comments have no inherent places, which need to be filled implicitly whe= n not explicitly, but have only those which are explicitly filled. This mea= ns, apparently, that the nature of the connection of a comment to its topic= has to be specified in (almost) every case, an added nuisance in speech bu= t probably a simplification in learning (and possible a reduction in the ne= ed for compounds, many of which are just to add a place to an existing pred= icate or rearrange those places). The bareness of comments means that comme= nt words can be raised to topics directly to do business as properties or e= vents, without a lot of extra detail.
These points are too sketchy to give any notion of the relative size, ease = or clarity of an &lang as here conceived, but at least it looks feasibl= e so far.
**

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@goo= glegroups.com.
For more options, visit this group at http://groups.google.com/grou= p/lojban?hl=3Den.

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@goo= glegroups.com.
For more options, visit this group at http://groups.google.com/grou= p/lojban?hl=3Den.




--
mu'o = mi'e .arpis.

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com.
For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.
--20cf307f34e4208c5604c4a939fd--