Return-Path: <@FINHUTC.HUT.FI:LOJBAN@CUVMB.BITNET> Received: from FINHUTC.hut.fi by xiron.pc.helsinki.fi with smtp (Linux Smail3.1.28.1 #1) id m0r1JA5-00006yC; Sat, 29 Oct 94 21:09 EET Message-Id: Received: from FINHUTC.HUT.FI by FINHUTC.hut.fi (IBM VM SMTP V2R2) with BSMTP id 5321; Sat, 29 Oct 94 21:10:10 EET Received: from SEARN.SUNET.SE (NJE origin MAILER@SEARN) by FINHUTC.HUT.FI (LMail V1.1d/1.7f) with BSMTP id 5318; Sat, 29 Oct 1994 21:10:09 +0200 Received: from SEARN.SUNET.SE (NJE origin LISTSERV@SEARN) by SEARN.SUNET.SE (LMail V1.2a/1.8a) with BSMTP id 8436; Sat, 29 Oct 1994 20:07:05 +0100 Date: Sat, 29 Oct 1994 12:46:18 -0600 Reply-To: Chris Bogart Sender: Lojban list From: Chris Bogart Subject: Re: any, opaque, transparent, xe'e... X-To: lojban@cuvmb.bitnet To: Veijo Vilva Content-Length: 2919 Lines: 57 >And one other thing... About the opaque/transparent thing... I have been >listening to the discussion for about a month (or more?), and I basically >know what is wrong with "any", but I can't figure out what in fact do >"opaque" andate, but my mind >usually just skips over these words, not being able to parse them. A transparent reference is a linguistic reference to something; an opaque reference is what *appears* to be a reference, but it doesn't *in fact* reference any particular thing. It's *kind of* like an uninstantiated variable. "I need that red box" is transparent, because, in context, there is some red box that the speaker and listener both know is being referred to specifically. "I need a red box" (in its usual interpretation) is opaque, because "a red box" doesn't refer to any particular box, really it describes the kind of need I have. We've been using "any" as shorthand for this situation, but that's not perfectly correct: consider this spooky Hallowe'en dialog: Santa Claus: "I need a red box to wrap Tommy's toy train." Elf: "Here, use this one." Santa: "No, I need a bigger one" Obviously not just "any" red box was good enough for Santa. It's also been suggested that "a red box" here actually does refer to something: one unidentified member of the set of red boxes which exist. But that's not strictly true either; consider: Santa: "I need a red box to wrap Tommy's toy train!" Elf: "I'll get some tape and red cardboard and make one for you" or even: Santa: "I need a red unicorn" Elf: "Tough luck. The unicorn is a mythical beast." You can't pin down what "a red box" is referring to because it doesn't refer to anything. It merely describes (some of) the needed thing's required characteristics. Notice that that only happens in certain contexts, where there's a sort of implied negative in the semantics of the verb, that isn't handled by the usual negation mechanisms: "need", "want", "lack", are grammatically positive but semantically negative. If you say "I smell a red box", or "I see a red box", or "I sit on a red box", there's a particular box or boxes being talked about, and the reference isn't opaque. I have a suspicion that the *ideal* logical solution to all this, if we were starting from scratch, is to eliminate words like nitcu, djica, and claxu from the lexicon, and find a way of communicating those concepts that is explicitly marked as negative. But I don't think that's very practical at this point. Realistically I think we have to use either Lojbab's or Jorge's marking schemes, or forbid opaque references altogether, using other mechanisms like "mi tanxe nictu" to get the point across. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Chris Bogart cbogart@quetzal.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~