From lojban+bncCIywt_XDCRDD0rzxBBoEjTIf-w@googlegroups.com Tue Jul 26 14:31:02 2011 Received: from mail-vw0-f61.google.com ([209.85.212.61]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1QlpDA-0001DN-5v; Tue, 26 Jul 2011 14:31:02 -0700 Received: by vws2 with SMTP id 2sf516089vws.16 for ; Tue, 26 Jul 2011 14:30:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:x-yahoo-newman-id:x-yahoo-newman-property :x-ymail-osg:x-yahoo-smtp:references:in-reply-to :x-apple-yahoo-original-message-folder:mime-version:message-id :x-mailer:from:x-apple-yahoo-replied-msgid:subject:date: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:sender:list-subscribe:list-unsubscribe :content-type:content-transfer-encoding; bh=UD+6YhHhwRaONg6uCvHjTvIvIknGamg/cejzl5lQ0ic=; b=YoWS7OYkdwTtG/PmK20N3XZwEw0jznoFUKPG+JKJUG/B874oAr4ONDl7ibGqvYsMIb pjv683Nb2i5uToPxluhhm0kGzeWy7qiuBxvKSW1Kkddv5wv8GL+zXY34Q/T3mk6YbHHD PoA63xfIXe5zI7vB1/bZFQUdtzFBsDzSPZ5+Y= Received: by 10.220.151.66 with SMTP id b2mr987512vcw.26.1311713603893; Tue, 26 Jul 2011 13:53:23 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.52.96.197 with SMTP id du5ls2131948vdb.1.gmail; Tue, 26 Jul 2011 13:53:22 -0700 (PDT) Received: by 10.52.98.130 with SMTP id ei2mr2296968vdb.9.1311713602695; Tue, 26 Jul 2011 13:53:22 -0700 (PDT) Received: by 10.52.98.130 with SMTP id ei2mr2296967vdb.9.1311713602664; Tue, 26 Jul 2011 13:53:22 -0700 (PDT) Received: from nm27-vm0.bullet.mail.ac4.yahoo.com (nm27-vm0.bullet.mail.ac4.yahoo.com [98.139.52.244]) by gmr-mx.google.com with SMTP id bv16si1115535vdc.1.2011.07.26.13.53.22; Tue, 26 Jul 2011 13:53:22 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 98.139.52.244 as permitted sender) client-ip=98.139.52.244; Received: from [98.139.52.193] by nm27.bullet.mail.ac4.yahoo.com with NNFMP; 26 Jul 2011 20:53:22 -0000 Received: from [98.139.52.168] by tm6.bullet.mail.ac4.yahoo.com with NNFMP; 26 Jul 2011 20:53:22 -0000 Received: from [127.0.0.1] by omp1051.mail.ac4.yahoo.com with NNFMP; 26 Jul 2011 20:53:22 -0000 X-Yahoo-Newman-Id: 440152.18115.bm@omp1051.mail.ac4.yahoo.com Received: (qmail 37189 invoked from network); 26 Jul 2011 20:53:21 -0000 X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 0lgGAXwVM1lEu77VpSQRa1KC4YQgpAnDZNJX9OX78VNuYvi ncAeU3MOW9TrJ_V4TVH5scotde0SFO8npj7ngF7TsNv0gNr8MVrPkxQNlvHd JeookQjrCB6MB8n2W8P6YHtBDmyZ_L34PENFT2fkGgVmp8mL5FeToXKKwvXY U07fL66wsAJmj_kapPxnFJEAQyluG9Myh47uJ2ksQJnNtRkWkmpISb_JyEZ8 9wWPu3q7EFEEoq922OSo4IYOP_cTN1IWvzh7Y.z.7oGhEHvlLSgaVlD1cM.8 DV72oG90UudPXdRYhaQroSNfMZ7D5UcdkmdUR6Z4lHhQMCvS7L4Ay9oPdxCt snReiuXoXiRs4VZiwRG0w3ChJw3rRadcXFcVfQqXQKeimNJKkC284basXSE8 sWDpopkJwRdIwxG4wgWfEVvqwC6VbxD7.CtHoxXR3z2aJPgdzHpiOQWfpPRe vnC5pnisLaUkpvLll7UotKv36lT_rs3fdCoXAqnHnP5g5GGtv6w07I.yZOG. 1K.vXmi.6U6_CAlJByl7NTUTgXH1_IPHcahH5lP0QfAxBKvgk9fyA0KYwomv IL0LLLw-- X-Yahoo-SMTP: xvGyF4GswBCIFKGaxf5wSjlg3RF108g- Received: from [192.168.1.68] (kali9putra@99.92.108.41 with xymcookie) by smtp110-mob.biz.mail.ac4.yahoo.com with SMTP; 26 Jul 2011 13:53:20 -0700 PDT References: <87BB9A86-430F-4F64-9CD4-D8A5BD33B69A@yahoo.com> <1311695892.73678.YahooMailRC@web81305.mail.mud.yahoo.com> In-Reply-To: X-Apple-Yahoo-Original-Message-Folder: AAlojbanery Mime-Version: 1.0 (iPad Mail 8G4) Message-Id: <38B81BB6-73B6-485D-9EC1-B9D85046F2B7@yahoo.com> X-Mailer: iPad Mail (8G4) From: "John E. Clifford" X-Apple-Yahoo-Replied-Msgid: 1_9400948_AHfHjkQAAW8PTi8JAAX6aGHXUFo Subject: Re: [lojban] bu'a Date: Tue, 26 Jul 2011 17:00:45 -0400 To: "lojban@googlegroups.com" X-Original-Sender: kali9putra@yahoo.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: best guess record for domain of kali9putra@yahoo.com designates 98.139.52.244 as permitted sender) smtp.mail=kali9putra@yahoo.com; dkim=pass (test mode) header.i=@yahoo.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: Sender: lojban@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=Apple-Mail-1-546882871 Content-Transfer-Encoding: 7bit --Apple-Mail-1-546882871 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1 Yes, making quantifier expressions into sumti makes for problems, since it = makes it seem they have referents rather than ranges (I note in passing tha= t what you *say her makes it sound like sumti were things rather than expre= ssions -- and I admit that thanks to JCB, Lojban does talk that way sometim= es). If you ignore their position, however, and just look at their form (ad= mitting again that having an implicit quantifier makes this somewhat harder= ) then you have an operator and a variable it binds an an occurrence of tha= t variable. In I, you are not allowed to infer "there is a" from "not not = there is a" but the ground for that is in the logic of"not", not of the qua= ntifier. Yes, the range of second order quantifiers is predicates, but, ba= rring the oddity of what you say earlier, this just what you *meant before.= =20 You second point seems to play on Russell's axiom of reducibility, which sa= ys that every higher order sentence (and in Russellthat is a lot more than = just second order) has an equivalent sentence in first order. The plausibil= ity of this derives from the fact that is true of the pro sties of predicat= es that we immediate think of: definition, transitivity, reflexivity, symme= try, subordination, and so on. It's generally thought not true by people w= ho still work with this system . And ignored by everyone else, who are off= doing other things, either totally first (like modern set theory) or manag= ing to do second order without this reliance (though perfectly happy to use= the related sentences as shortcuts where they clarify and are independentl= y justified). Ro bu'a zo'u ganai ge ge da bu'a de gi roda rode rodi zo'u ganai ge da bu'a= de gi de bu'a di gi da bu'a di gi roda rode zo'u ganai da bu'a de gi de b= u'a da gi rada zo'u da bu'a da. ( second order but highly reduced). The real gripe is the lack of clear rules for giving characteristic functio= ns ("predicates" in the confused language that is common here). Sent from my iPad On Jul 26, 2011, at 14:35, Ian Johnson wrote: > What is hackish about it is the syntax. In {ro bu'a zo'u da bu'a}, {ro bu= 'a} is syntactically a sumti, consisting, presumably, of all x1's of whatev= er referent the {bu'a} ultimately has (thinking classically; in intuitionis= tic logic, what I am saying is not entirely sound), since that's what it me= ans elsewhere. And yet then the thing that is actually quantified over is a= collection of predicates. It's just an arbitrary decision plopped into the= CLL, changing the type of a variable abruptly. My gripe about it is irrati= onally amplified by my irrational mental attempts to statically type Lojban= , but even putting that aside I'd say it's a valid gripe, albeit irrelevant= from a practical standpoint since predicate quantification has seen no use= so far as far as I know, except in my example here. >=20 > We're also missing second order predicates, or at least things that serve= as convenient required predicates in second order discussions, in general.= Saying something like "{mintu} is the opposite of {drata}", even with {me'= ei} (of selma'o LE, which converts selbri into abstract predicate sumti; I = do NOT think quoted words are suitable as placeholders for abstract predica= tes), becomes: > me'ei mintu cu dukti me'ei drata ....???? > and I ultimately have no way of writing down the dukti3. (I would be plea= sed if you could, actually.) The only precise way of saying this (yes, I ad= mit the English is as imprecise as a statement involving {dukti} with no du= kti3, but I hope you can see the precise meaning that I want to encapsulate= ) that I can see is first order to its core: > ro da ro de ro di zo'u go da de di mintu gi da de di to'e drata >=20 > mu'o mi'e latros > On Tue, Jul 26, 2011 at 11:58 AM, John E Clifford = wrote: > I'm not sure what you take as hackish about it. Simply allows quantifier= s over predicate variables, which is all that is required. To be sure, it = is does not seem to allow such quantifiers any place but prenex ('ko'a (cu)= suo bu'a' don't seem to compute), but the embedded quantifiers are a main = source of difficulty (pace xorxes) in reconstructing the logic of Lojban, s= o this may not be a flaw. What then is hackish? The pattern of real Logic= is followed (less a mess of sub- and superscripts that are largely irrelev= ant to Lojban). Yes, Lojban is based on first order, but, then, so is seco= nd order and Lojban allows that extension (and, in principle, all the other= orders on up). > As I said, part of the problem is to figure just what a predicate is in L= ojban. There are several candidates (sticking to unary predicates for simp= licity): the things that have the property, the set of things that have the= property, the characteristic function of that set, and the property, which= may or may not be what a Montagovian would call a property. Three of thes= e have clear expressions in Lojban, but the characteristic function does no= t really, but is the best candidate for the predicate in what follows in se= cond order claims. There is talk of the lambda calculus but it is unimpleme= nted, so far as I can see (and is second order). >=20 > From: Ian Johnson > To: lojban@googlegroups.com > Sent: Tue, July 26, 2011 9:24:10 AM > Subject: Re: [lojban] bu'a >=20 > Erm, poor phrasing; I meant that there is no easy way to get between thos= e three things.=20 >=20 > .u'u .i mu'o mi'e latros >=20 > On Tue, Jul 26, 2011 at 10:22 AM, Ian Johnson wr= ote: > Quantification over predicates was implemented in a horrifyingly hackish = way. This alone is a problem, in my opinion. There is also, at least not in= the main body of the language, an easy way to go from predicate-as-functio= n (selbri) to predicate-as-concrete-object (typical sumti) to predicate-as-= abstract-object. >=20 > Lojban is definitely based on FOPL, though, not SOPL, and not a bizarre h= ybrid of the two.=20 >=20 > mu'o mi'e latros >=20 > On Sun, Jul 24, 2011 at 2:51 PM, John E. Clifford = wrote: > Lojban isn't clearly of one order or the other, since it treats sets and = properties and the like on a par with tree and dogs. There is no particula= r problem in grammar or vocabulary to treating properties of predicates and= quantification over them. There are some arguments about the correct way = to express a predicate as an argument, but that seems to revolve around jus= t what a predicate is in Lojban ontology. All the answers yield grammatica= l and intelligible results, though sometimes different ones. None of them = seem particularly stilted, but I haven't seen enough cases to get a feel fo= r that. >=20 > Sent from my iPad >=20 > On Jul 24, 2011, at 14:13, Ian Johnson wrote: >=20 >> I think bu'a/bu'e/bu'i would be much much much more useful if Lojban wer= e a second order language, because then we could talk about the existence o= f predicates with desired properties in a non-stilted fashion. As a first o= rder language, though, with second order mechanisms requiring stilted langu= age, I don't think bu'a/bu'e/bu'i are especially useful. >> =20 >> mu'o mi'e latros >> =20 >> On Sun, Jul 24, 2011 at 12:01 PM, tijlan wrote: >> What is your view on the bu'a series? Potentially useful? Totally >> pointless? I've never used it myself, but I could be missing some >> important aspect of Lojban as a logical language. >>=20 >> mu'o mi'e tijlan >>=20 >> -- >> You received this message because you are subscribed to the Google Group= s "lojban" group. >> To post to this group, send email to lojban@googlegroups.com. >> To unsubscribe from this group, send email to lojban+unsubscribe@googleg= roups.com. >> For more options, visit this group at http://groups.google.com/group/loj= ban?hl=3Den. >>=20 >>=20 >> --=20 >> You received this message because you are subscribed to the Google Group= s "lojban" group. >> To post to this group, send email to lojban@googlegroups.com. >> To unsubscribe from this group, send email to lojban+unsubscribe@googleg= roups.com. >> For more options, visit this group at http://groups.google.com/group/loj= ban?hl=3Den. >=20 > --=20 > 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@googlegr= oups.com. > For more options, visit this group at http://groups.google.com/group/lojb= an?hl=3Den. >=20 >=20 > --=20 > 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@googlegr= oups.com. > For more options, visit this group at http://groups.google.com/group/lojb= an?hl=3Den. > --=20 > 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@googlegr= oups.com. > For more options, visit this group at http://groups.google.com/group/lojb= an?hl=3Den. >=20 > --=20 > 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@googlegr= oups.com. > For more options, visit this group at http://groups.google.com/group/lojb= an?hl=3Den. --=20 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. --Apple-Mail-1-546882871 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1
Yes, making quantifier expressions int= o sumti makes for problems, since it makes it seem they have referents rath= er than ranges (I note in passing that what you *say her makes it sound lik= e sumti were things rather than expressions -- and I admit that thanks to J= CB, Lojban does talk that way sometimes). If you ignore their position, how= ever, and just look at their form (admitting again that having an implicit = quantifier makes this somewhat harder) then you have an operator and a vari= able it binds an an occurrence of that variable.  In I, you are not al= lowed to infer "there is a" from "not not there is a" but the ground for th= at is in the logic of"not", not of the quantifier.  Yes, the range of = second order quantifiers is predicates, but, barring the oddity of what you= say earlier, this just what you *meant before.  
You second= point seems to play on Russell's axiom of reducibility, which says that ev= ery higher order sentence (and in Russellthat is a lot more than just secon= d order) has an equivalent sentence in first order. The plausibility of thi= s derives from the fact that is true of the pro sties of predicates that we= immediate think of: definition, transitivity, reflexivity, symmetry, subor= dination, and so on.  It's generally thought not true by people who st= ill work with this system .  And ignored by everyone else, who are off= doing other things, either totally first (like modern set theory) or manag= ing to do second order without this reliance (though perfectly happy to use= the related sentences as shortcuts where they clarify and are independentl= y justified).

Ro bu'a zo'u ganai ge ge da bu'a de = gi roda rode rodi zo'u ganai ge da bu'a de gi de bu'a di gi da bu'a di &nbs= p;gi roda rode zo'u ganai da bu'a de gi de bu'a da gi rada zo'u da bu'a da.=  ( second order but highly reduced).

The rea= l gripe is the lack of clear rules for giving characteristic functions ("pr= edicates" in the confused language that is common here).
Sent from my iP= ad

On Jul 26, 2011, at 14:35, Ian Johnson <blindbravado@gmail.com> wrote:

What is hackish about it is th= e syntax. In {ro bu'a zo'u da bu'a}, {ro bu'a} is syntactically a sumti, co= nsisting, presumably, of all x1's of whatever referent the {bu'a} ultimatel= y has (thinking classically; in intuitionistic logic, what I am saying is n= ot entirely sound), since that's what it means elsewhere. And yet then the = thing that is actually quantified over is a collection of predicates. It's = just an arbitrary decision plopped into the CLL, changing the type of a var= iable abruptly. My gripe about it is irrationally amplified by my irrationa= l mental attempts to statically type Lojban, but even putting that aside I'= d say it's a valid gripe, albeit irrelevant from a practical standpoint sin= ce predicate quantification has seen no use so far as far as I know, except= in my example here.

We're also missing second order predicates, or at least things that ser= ve as convenient required predicates in second order d= iscussions, in general. Saying something like "{mintu} is the opposite of {= drata}", even with {me'ei} (of selma'o LE, which converts selbri into abstr= act predicate sumti; I do NOT think quoted words are suitable as placeholde= rs for abstract predicates), becomes:
me'ei mintu cu dukti me'ei drata ....????
and I ultimately have no way o= f writing down the dukti3. (I would be pleased if you could, actually.) The= only precise way of saying this (yes, I admit the English is as imprecise = as a statement involving {dukti} with no dukti3, but I hope you can see the= precise meaning that I want to encapsulate) that I can see is first order = to its core:
ro da ro de ro di zo'u go da de di mintu gi da de di to'e drata

mu'o= mi'e latros
On Tue, Jul 26, 2011 at 11:58 AM= , John E Clifford <kali9putra@yahoo.com&g= t; wrote:
I'm not sure what you take as hack= ish about it.  Simply allows quantifiers over predicate variables, whi= ch is all that is required.  To be sure, it is does not seem to allow = such quantifiers any place but prenex ('ko'a (cu) suo bu'a' don't seem to c= ompute), but the embedded quantifiers are a main source of difficulty (pace= xorxes) in reconstructing the logic of Lojban, so this may not be a flaw.&= nbsp; What then is hackish?  The pattern of real Logic is followed (le= ss a mess of sub- and superscripts that are largely irrelevant to Lojban).&= nbsp; Yes, Lojban is based on first order, but, then, so is second order an= d Lojban allows that extension (and, in principle, all the other orders on = up).
As I said, part of the problem is to figure just what a predicate is i= n Lojban.  There are several candidates (sticking to unary predicates for simplicity)= : the things that have the property, the set of things that have the proper= ty, the characteristic function of that set, and the property, which may or= may not be what a Montagovian would call a property.  Three of these = have clear expressions in Lojban, but the characteristic function does not = really, but is the best candidate for the predicate in what follows in seco= nd order claims. There is talk of the lambda calculus but it is unimplement= ed, so far as I can see (and is second order).


= From: Ian Johnson <blindbravado@gmail.com>
To: lojban@googlegroups.com
Sent: Tue, July 26, 2011 9:24:10 AMSubject: Re: [lojban] bu'a<= br>

Erm, poor phrasing; I meant that there is no easy way to get between those = three things.

.u'u .i mu'o mi'e latros

On Tue, Jul 26, 2011 at 10:22 AM, Ian Johnson <<= a rel=3D"nofollow" href=3D"mailto:blindbravado@gmail.com" target=3D"_blank"= >blindbravado@gmail.com&g= t; wrote:
Quantification over predicates was implement= ed in a horrifyingly hackish way. This alone is a problem, in my opinion. T= here is also, at least not in the main body of the language, an easy way to= go from predicate-as-function (selbri) to predicate-as-concrete-object (ty= pical sumti) to predicate-as-abstract-object.

Lojban is definitely based on FOPL, though, not SOPL, and not a bizarre= hybrid of the two.

mu'o mi'e latros

On Sun, Jul 24, 2011 at 2:51 PM, John E= . Clifford <ka= li9putra@yahoo.com> wrote:
Lojban isn't clearly of one order = or the other, since it treats sets and properties and the like on a par wit= h tree and dogs.  There is no particular problem in grammar or vocabul= ary to treating properties of predicates and quantification over them. &nbs= p;There are some arguments about the correct way to express a predicate as = an argument, but that seems to revolve around just what a predicate is in L= ojban ontology.  All the answers yield grammatical and intelligible re= sults, though sometimes different ones.  None of them seem particularl= y stilted, but I haven't seen enough cases to get a feel for that.

Sent from my iPad

On Jul 24, 20= 11, at 14:13, Ian Johnson <b= lindbravado@gmail.com> wrote:

=
I think bu'a/bu'e/bu'i would be much much much more useful if Lojban w= ere a second order language, because then we could talk about the existence= of predicates with desired properties in a non-stilted fashion. As a = first order language, though, with second order mechanisms requiring stilte= d language, I don't think bu'a/bu'e/bu'i are especially useful.
 
mu'o mi'e latros
 
On Sun, Jul 24, 2011 at 12:01 PM, tijlan <jbotijlan@gmail.com= > wrote:
What is your view on the bu'a series?= Potentially useful? Totally
pointless? I've never used it myself, but I= could be missing some
important aspect of Lojban as a logical language.

mu'o mi'e tijlan
--
You received this message because you a= re 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+unsu= bscribe@googlegroups.com.
For more options, visit this group at http://groups.google.co= m/group/lojban?hl=3Den.


--
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.co= m.
For more options, visit this group at http://groups.google.com/group/lojba= n?hl=3Den.

--
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/lojba= n?hl=3Den.


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

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To post to this group, send email to lojban@go= oglegroups.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=3Den= .

--
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=3Den.

--
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.
--Apple-Mail-1-546882871--