Received: from mail-ob0-f189.google.com ([209.85.214.189]:49653) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1SpTIB-0005YK-GS; Thu, 12 Jul 2012 16:59:39 -0700 Received: by obbun3 with SMTP id un3sf3103329obb.16 for ; Thu, 12 Jul 2012 16:59:25 -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=LNvYQydMGydSDYh6EixTFJtZPd9a8v/QEzVh0wp702k=; b=1DhcQdLEjdT1isGVJdQAaqUMn5CJon6W+E50kJeq5qG3tcNeIxEb8GdfkBIlMifxpd FMkU64z22kOBxVP2fQ6uu9bNBw+GcWnrpFKvoOL8EyQkmMYPyDjBMhYCTf0h0X9DbPnP nBMs5VLpHkwgc3xRJvHaBRx1x9Zy42ItCLCvE= Received: by 10.52.155.207 with SMTP id vy15mr21651vdb.13.1342137564909; Thu, 12 Jul 2012 16:59:24 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.220.230.4 with SMTP id jk4ls1477968vcb.4.gmail; Thu, 12 Jul 2012 16:59:24 -0700 (PDT) Received: by 10.52.75.161 with SMTP id d1mr152200vdw.2.1342137564141; Thu, 12 Jul 2012 16:59:24 -0700 (PDT) Received: by 10.52.75.161 with SMTP id d1mr152198vdw.2.1342137564120; Thu, 12 Jul 2012 16:59:24 -0700 (PDT) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by gmr-mx.google.com with ESMTPS id l12si284175vdf.3.2012.07.12.16.59.24 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 Jul 2012 16:59:24 -0700 (PDT) Received-SPF: pass (google.com: domain of rpglover64@gmail.com designates 209.85.212.54 as permitted sender) client-ip=209.85.212.54; Received: by mail-vb0-f54.google.com with SMTP id v11so2038455vbm.41 for ; Thu, 12 Jul 2012 16:59:24 -0700 (PDT) Received: by 10.220.116.3 with SMTP id k3mr113015vcq.26.1342137563844; Thu, 12 Jul 2012 16:59:23 -0700 (PDT) MIME-Version: 1.0 Sender: lojban@googlegroups.com Received: by 10.58.171.7 with HTTP; Thu, 12 Jul 2012 16:59:03 -0700 (PDT) In-Reply-To: <4FFF534B.9010509@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> <4FFF534B.9010509@gmail.com> From: ".arpis." Date: Thu, 12 Jul 2012 19:59:03 -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.212.54 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=f46d043c7aacbb91ef04c4aac0fd X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / --f46d043c7aacbb91ef04c4aac0fd Content-Type: text/plain; charset=ISO-8859-1 I'm not sure I understand the predicate-argument structure well enough to do so. Could you give an example of how it would look with normal variables and explain the meaning of the example? On Thu, Jul 12, 2012 at 6:44 PM, And Rosta wrote: > .arpis., On 12/07/2012 23:09: > > 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. >> > > Can you give an example of how it would work if applied to a > predicate--argument structure? I can't follow the wikipedia article enough > to see how it would work (-- setting aside the memory limitation problem > you mention). > > On Thu, Jul 12, 2012 at 2:31 PM, And Rosta > 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 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> 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 < >> 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 > 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 < >> 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 . >> > > -- > 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. --f46d043c7aacbb91ef04c4aac0fd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I'm not sure I understand the predicate-argument structure well enough = to do so. Could you give an example of how it would look with normal variab= les and explain the meaning of the example?

On Thu, Jul 12, 2012 at 6:44 PM, And Rosta <and.rosta@gmail.com><= /span> wrote:
.arpis., On 12/07/2012 23:09:

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://en.wikipedia.org/wiki/De_Bruijn_index), but thi= s fails the requirement of fitting in human memory.

Can you give an example of how it would work if applied to a predicate--arg= ument structure? I can't follow the wikipedia article enough to see how= it would work (-- setting aside the memory limitation problem you mention)= .

On Thu, Jul 12, 2012 at 2:31 PM, And Rosta <and.rosta@gmail.com <mailto:and.rosta@gmail.com>&g= t; wrote:

=A0 =A0 Let me try harder to explain:


=A0 =A0 Take a variety of predicate logic consisting of predicates, quantif= iers and variables. In normal predicate logic notation, if a given variable= is an argument of more than one predicate, it gets repeated. And every bou= nd variable is notated at least twice, once where it is shown bound by quan= tifier and once where it is argument of a predicate. But this is one and th= e same variable; the repetition is a mere notational device necessary to li= nearize the string.

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

=A0 =A0 That's the basic data structure for predicate--argument structu= re. A 2-dimensional notation can notate it without redundancy. But spoken l= anguage 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 taxi= ng on the memory that the advantages of its logical explicitness and unambi= guousness are not outweighed?

=A0 =A0 --And.

=A0 =A0 John E Clifford, On 12/07/2012 17:17:

=A0 =A0 =A0 =A0 As far as I can figure from the limited information, &&= #39;s language differs from Logjam in two significant respects.
=A0 =A0 =A0 =A0 1. Instead of a predicate with various arguments dripping f= rom it, the core utterance is an argument (topic, say) with dangling predic= ates (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 ca= se of existential graphs and general topological considerations, however, s= uggest that anaphora will be needed in one-dimensional speech. The usual pr= oblems with that are simplified by the canonical location of topics. Multip= le topics increase the complexity of this but not its basic simplicity. Com= ments come and go (naturally) while topics run on and on (and so are always= available for connection).
=A0 =A0 =A0 =A0 2. Comments have no inherent places, which need to be fille= d implicitly when not explicitly, but have only those which are explicitly = filled. This means, apparently, that the nature of the connection of a comm= ent to its topic has to be specified in (almost) every case, an added nuisa= nce in speech but probably a simplification in learning (and possible a red= uction 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.
=A0 =A0 =A0 =A0 These points are too sketchy to give any notion of the rela= tive size, ease or clarity of an &lang as here conceived, but at least = it looks feasible so far.
=A0 =A0 =A0 =A0 **

=A0 =A0 =A0 =A0 --
=A0 =A0 =A0 =A0 You received this message because you are subscribed to the= Google Groups "lojban" group.
=A0 =A0 =A0 =A0 To post to this group, send email to lojban@googlegroups.com <mail= to:lojban@goog= legroups.com>.
=A0 =A0 =A0 =A0 To unsubscribe from this group, send email to lojban+unsubs= cribe@ googlegroups.c= om <mailto:lojban%2Bunsubscribe@googlegroups.com>. =A0 =A0 =A0 =A0 For more options, visit this group at http://groups.google.com/ group/lojb= an?hl=3Den <http://groups.google.com/group/lojban?hl=3Den>= ;.



=A0 =A0 --
=A0 =A0 You received this message because you are subscribed to the Google = Groups "lojban" group.
=A0 =A0 To post to this group, send email to lojban@googlegroups.com <mailto:lojban@googlegroups= .com>.
=A0 =A0 To unsubscribe from this group, send email to lojban+unsubscribe@ <= a href=3D"http://googlegroups.com" target=3D"_blank">googlegroups.com &= lt;mailto:lojban%2Bunsubscribe@googlegroups.com>.
=A0 =A0 For more options, visit this group at http://groups.google.com/ group/lojban?hl=3D= en <http://groups.google.com/group/lojban?hl=3Den>.





--
mu'o mi'e .arpis.

--
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.
--f46d043c7aacbb91ef04c4aac0fd--