[lojban] Questions about jorne

[Oren]

The jorne page on sourceforge [http://jorne.sourceforge.net/] doesn't mention OWL or appear to have any source code... is there a newer specification or codebase that I'm missing? The PEG parser?

As for the ideas proposed on the page, I still need to be sold. There seems to be overlap with the W3C incubator projects for representing Wordnet in RDF/OWL http://www.w3.org/TR/wordnet-rdf/, and quite frankly, lojban's minimal and prescriptive vocabulary doesn't seem to offer much application here.

Two separate overlapping W3C incubator projects seem to be more appropriate for semantic querying, Common Web Language (semantic representation) http://www.w3.org/2005/Incubator/cwl/XGR-cwl-20080331/ and Emotional Markup Language http://www.w3.org/2005/Incubator/emotion/XGR-emotionml-20081120/.

Lojban, as a human language, can't offer what these robust proposals describe-- that is, you can't really argue that lojban is any more 'readable' than these languages, nor believe that it would be briefer or more thorough; but it may be fun to try and define the entire lojban vocabulary using these technologies. Or maybe that's what you meant all along?

co'o mi'e korbi

On Thu, Apr 15, 2010 at 19:49, Brian Eubanks <br...@buildsoftware.com> wrote:

Hi Oren,

We corresponded last year about the Jorne (Lojban RDF) project I am trying to get started.

The idea of using a Wordnet type approach is excellent. In fact, I would love to see a LojWordNet in association with the Jorne OWL mapping.

Are you still interested in working on an OWL mapping for Lojban gismu? If so, I would like you to join the Sourceforge Jorne project. The growing amount of linked data makes this a great time to do this.

I am working with the PEG parser to import simple sentences into an RDF triple store with the hope of converting between SPARQL and Lojban queries. My Lojban is not even baby talk level yet, which is where I could use your help too. I've been a lurker in the Lojban space but haven't spent time to learn it.

Regards,
Brian Eubanks

Sent from my iPhone

On Apr 15, 2010, at 3:52 AM, Oren <get....@gmail.com> wrote:

I like the idea of categories (or... tags!), I think the wiki is the
place for it to happen, and I also think we shouldn't start from
scratch. The thesaurus on the wiki page already segregates all gismu
into hierarchical categories. We can make a page template that allows
people to add "lujvo requests" to a category. A sister project to
consider would be fleshing out that same ontology with the existing
specialized lujvo lists and the lujvo flat file.

I would also think that English/natlang glosses for the categories
should be optional while lojban section titles be mandatory and
default, for clarity.

Back to the original topic of finding a minimal wordlist for a
dictionary, I think the real forward-thinking approach would be to
find some sufficiently open project similar to EuroWordNet [a
multilingual WordNet], and then extracting a set number of unique
*syslinks* (word senses), so that when we sit down to define 'spring'
we don't have to remember jumping, metal coils and le printemps all by
our erring-human selves.

We could either use an arbitrary limit and go by frequency, and/or go
for all syslinks that contain an arbitrary number of constituent
languages. For example, only bother with 50% of all word senses that
appear in three or more languages.

co'o mi'e korbi

On Thu, Apr 15, 2010 at 15:13, Lindar <lindar...@yahoo.com> wrote:

My absolutely fantastic idea that donri/kribacr started and never
finished (or never even started, but definitely came up before I
thought of it [but it's still my idea]) is/was/will be to have groups
of people select topics, and then go through and come up with as many
words related to that topic as possible. I got this idea one day as I
was sticking masking tape to pretty much everything around my
apartment and writing the Lojban word for it in sharpie. I came across
the simple fact that jvs didn't have words for "pot", "kitchen",
"frying pan", etc., so I came up with words for them, and I think at
least "kitchen" (jupku'a) is up there. I tried this again with
computer terminology and it completely failed as nobody could agree
properly on things (like "window", on which I still harshly/
obnoxiously/rudely/insultingly disagree with xorxes).

Rather than having one person sit through some big gehorsenshitfesten
(parden my German) trying to pick out the most common concepts in the
universe, why don't we use the wiki idea and create "conversational
categories" under which we can place words (probably a lot of fu'ivla
and lujvo) relevant to the topic. This will generate a much larger and
relevant body of information, and it's a -much- less daunting task.
For example, I am a recording engineer, so I would be likely to start
a "recording technology" topic, and possibly contribute to the "music"
topic as I would be more likely than anybody else to need/use words
like "Hertz"/"kHz", "microphone", "nearfield monitors", "synthesizer",
"MIDI", "mixing console", "bass", "treble", and I would probably be
more qualified to determine what kind of terminology in Lojban is the
most suitable. I'd also be fairly interested in the "kitchen and
cooking" topic, and I think a great many a newbie would be very
interested in the "household objects" topic, which would probably
include a pointer to the "kitchen and cooking" topic and maybe even a
"bathroom and hygiene" topic. This way people find what interests them
and contribute to topics that they enjoy, which doesn't necessarily
give an accurate picture of common usage based on an average through
world cultures, but definitely gives a good sampling of words to use
in conversation for the types of conversation that people learning
Lojban would have. It works as a double edged sword (of handiness) in
that we have people that are going to enjoy working because they're
learning how to talk about things that interest them by contributing
(which means things are more likely to get added, being that it's fun
and not a chore) -AND- that we have quick 'topic reference'
dictionaries so you can just leave the list open and peak through to
make it easier to carry on conversations about what an arse your
government leader is without having to poke through a list for ten
minutes while the conversation has already passed because you wanted a
word for "idiot" and jvs only had "stupid" as a gloss word for
tolmencre. (Bad example, you get the picture.)

Perhaps we can quickly brainstorm a few major topics just to have
something up on a wiki?

household items
kitchen and cooking
bathroom and hygiene
sports and spectating
automotive and driving
computer ((hot topic, prone to arguments))
music
politics and law
school and education
work and the workplace
friends and family

The idea would be to have a big list of topics (and possibly
subtopics), and on the pages of each we have brief glosses with Lojban
words, with links to a page detailing the place structure, examples of
usage, actual usage example if available, and potentially a relevant
image (for those that learn by seeing and not reading).

Perhaps under "household items" is "garage", and on the page for that
it includes a little link for "see section: automotive and driving",
and perhaps even "garage" is also located under "automotive and
driving" or somesuch.

Neatonifty idea, right?

--
You received this message because you are subscribed to the Google Groups "lojban" group.
To post to this group, send email to loj...@googlegroups.com.
To unsubscribe from this group, send email to lojban+un...@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 loj...@googlegroups.com.
To unsubscribe from this group, send email to lojban+un...@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 loj...@googlegroups.com.
To unsubscribe from this group, send email to lojban+un...@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 loj...@googlegroups.com.
To unsubscribe from this group, send email to lojban+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/lojban?hl=en.

[Lindar]

> Lojban, as a human language, can't offer what these robust proposals
> describe-- that is, you can't really argue that lojban is any more
> 'readable' than these languages, nor believe that it would be briefer or
> more thorough; but it may be fun to try and define the entire lojban
> vocabulary using these technologies. Or maybe that's what you meant all
> along?

Uhhh... that looks like a slightly unreadable version of Lojban using
English words.
I really fail to see the difference here, so I gather you're saying
"Lojban can't do what this thing does that looks like a shitty/
inadequate version of Lojban." ? I'm really confused about your
meaning.

[Oren]

Lojban is meant for human communication, one result of this is a
limited vocabulary size, and reliance on compounds.

CWL and EmotionML are not meant for human communication, and rely on
[1] extensive and customizable vocabulary, and [2] a directed graph
markup.

[1] From the specifications: “Concepts included in any natural
language can be the vocaburary of CWL.“
[1] From the EmotionML specifications, "users can create their custom
vocabularies."
[2] Note the graph structure of CWL:
{cwl.unl}
tim(begin.@entry.@past,long ago)
mod(city.@def,Babylon)
plc(begin.@entry.@past,city.@def)
agt(begin.@entry.@past,people.@def)
obj(begin.@entry.@past,build.@past)
agt(build,people.@def)
obj(build,tower)
aoj(huge,tower)
aoj(seem.@past,tower)
obj(seem.@past,reach.@begin.@soon)
obj(reach.@begin.@soon,tower)
gol(reach.@begin.@soon,heaven.@def.@pl)
{/cwl.unl}
[2] EmotionML uses the following ontologies:
Attitudes
Established emotion
Emergent emotion (full-blown)
Emergent emotion (suppressed)
Moods
Partial emotion (topic shifting)
Partial emotion (simmering)
Stance towards person
Stance towards object/situation
Interpersonal bonds
Altered state of arousal
Altered state of control
Altered state of seriousness
Emotionless

...Can lojban allow that? A brief embedded triple structure for a
forty-one-type-of-relation directed graph markup? Sure, but but it
wont be intelligible lojban.

A limitless vocabulary? The discussion began because we're trying to
work up to a 6000 word dictionary... endless additions don't seem
feasible.

An expansion of emotional ontology, and allowing of custom vocabulary?
Doesn't seem that Lojban is designed to be that flexible.

My above questions are probably due to my misunderstanding of the
specifications of Jorne; it makes much more sense to try and describe
[finite] lojban in terms of these frameworks, and not try and, like
these frameworks, attempt to describe [infinite] natural language text
and emotion.

And I could be way off. I haven't seen any source code either.

[Lindar]

NOTE: Skip to the bottom for the short version.

> [1] From the specifications: “Concepts included in any natural
> language can be the vocaburary of CWL.“

Oh, so you're suggesting we use this to create some kind of...
documentation? Translator? I still don't get what you mean...

> [1] From the EmotionML specifications, "users can create their custom
> vocabularies."

Nifty.

> [2] Note the graph structure  of CWL:

[Bunch of BS cut out.]

Yeah, I have no idea what that means, and consequently is of no use to
me.
Looks random BS somebody wrote down to stick on a screen to look like
they're programming something when they don't have any idea how to
actually programme, rather than anything actually intelligible.

> ...Can lojban allow that?

What? All that emotion schtuphs? Yeah, it can, newbies pretty much use
nothing but that. Every single little thing you described on that
emoticrap list is feasible in Lojban, AFAIK.

> A brief embedded triple structure for a
> forty-one-type-of-relation directed graph markup? Sure, but but it
> wont be intelligible lojban.

Yeah, that sounds like a bunch of crap made up for a Star Trek script.
Simple English, please. =D

> A limitless vocabulary? The discussion began because we're trying to
> work up to a 6000 word dictionary... endless additions don't seem
> feasible.

You seem to be missing some big key here. We are, right now,
documenting vocabulary to be used in common conversation, which we
will begin to translate into Lojban and develop any missing words or
terminology. Just because we don't have them doesn't mean we aren't
going to have them at all ever. There are probably some 2 to 6 million
intelligible lujvo that can be created (just taking a guess at
1600x1600x1600 and assuming that a lot of them are going to be
useless), plus fu'ivla borrowed from native languages of origin (most
commonly Greek or Latin I would assume due to scientific standards).
4700-some words aren't really a big deal in the scope of things.
Maybe, instead of being pessimistic, you could help the BPFK
translation project or Conversation Guide project so we can actually
have a finished product to use as source-material for a dictionary? =D

> An expansion of emotional ontology, and allowing of custom vocabulary?
> Doesn't seem that Lojban is designed to be that flexible.

...uh...yeah, actually, it is. lujvo and fu'ivla are designed for
exactly that, unless I'm missing your meaning.
As for the "emotional ontology"... uhh... go play around with selma'o
UI or something... I'm not sure really what you're trying to get at
with this part.

> My above questions are probably due to my misunderstanding of the
> specifications of Jorne; it makes much more sense to try and describe
> [finite] lojban in terms of these frameworks, and not try and, like
> these frameworks, attempt to describe [infinite] natural language text
> and emotion.

This looks like bad Am-Eng. Did you mean "It makes much more sense to
try to describe finite lojban in terms of these frameworks rather than
to try to describe infinite natural language text and emotion." ? Cos
if not, I have no clue what you're trying to say. If that is what you
meant, then I agree in the context of choosing one option or the
other, but I fail to see what any of this has to do with anything (and
if it isn't, could you please rewrite it in Lojban?). Why did you
bring it up? What is it meant to accomplish? It seems that you're
suggesting an attempt to try to document Lojban with this, which has
absolutely nothing to do with the dictionary effort then, and why did
you bring up the dictionary in the first place? We don't need a method
of defining Lojban using some kind of programming language that uses
single English gloss words as that's pretty much what we've got now,
and that's why we're having the problems we're having right now.

We need formal, human readable, plain-text, simple English
translations for stupid people, and we need formal definitions for
pretty much every cmavo in the ma'oste. I think whatever this is that
you're proposing is completely unrelated to the dictionary effort, so
let's drop that idea entirely from the conversation.

What, EXACTLY, are you suggesting we do with 'jorne', and what is it
meant to accomplish?

[Bob LeChevalier, President and Founder - LLG]

Lindar wrote:
> NOTE: Skip to the bottom for the short version.

While Oren quoted your post in his reply, he was not replying to you,
but rather to Brian Eubanks who posted about his Jorne project.

http://jorne.sourceforge.net/

Jorne is not a dictionary, and only vaguely related to a dictionary
project, being more akin to the sort of artificial intelligence
applications I mentioned a few days ago. It might be possible to
explain it in non-technical English you seem to want, I'm not the one to
do it. But it involves using Lojban as a tool for exploring data that
has been appropriately linked for such exploration.

>>A limitless vocabulary? The discussion began because we're trying to
>>work up to a 6000 word dictionary... endless additions don't seem
>>feasible.
>
> You seem to be missing some big key here. We are, right now,
> documenting vocabulary to be used in common conversation,

Jorne would need vocabulary documented to be used in "computer
conversation" of a sort. That vocabulary has to be defined in a certain
way to be so usable.

> Maybe, instead of being pessimistic, you could help the BPFK
> translation project or Conversation Guide project so we can actually
> have a finished product to use as source-material for a dictionary? =D

There are many other projects going on in the Lojban world besides those
two.

> I think whatever this is that
> you're proposing is completely unrelated to the dictionary effort,

Almost completely so, but it could certainly make use of any dictionary
results, if the dictionary were designed with such application in mind.

> so let's drop that idea entirely from the conversation.

He posted under a different subject line, indicating that it was a
different conversation.

> What, EXACTLY, are you suggesting we do with 'jorne', and what is it
> meant to accomplish?

See the link above (and the links therein), but they use the jargon of
computer-language design and AI.

http://en.wikipedia.org/wiki/Semantic_web
http://www.w3.org/TR/owl-features/

are two that seemed relevant to Oren's comments, but I won't pretend to
fully understand them myself.

lojbab
--
Bob LeChevalier loj...@lojban.org www.lojban.org
President and Founder, The Logical Language Group, Inc.

[Oren]

Sorry for not being more clear, this has nothing to do with the
dictionary project (hence the new subject line). Perhaps it was a
mistake to message the whole list; my question regards the goals of a
particular project, namely 'jorne.'

My question was 'what are the goals?' The citations were to
demonstrate similar projects are designing complex languages from
scratch to meet similar goals, as devil's advocacy arguing against
adapting Lojban for such tasks, my interpretation of jorne's
description.

.u'u co'o ro do

[Brian D. Eubanks]

Unfortunately I am just now getting back to my computer to answer
comments. I had not originally intended to respond to the whole list,
so my apologies for the thread getting mangled. But since the
discussion has escaped onto the list now, I'll explain a little about
the jorne project to anyone who might find it interesting. I'll try to
straddle the line between being readable and technical, for those who
have no idea what RDF is.

The primary goal of jorne is creating intelligent systems that combine
Lojban with Semantic Web technologies (see
http://en.wikipedia.org/wiki/Semantic_Web).

The project is currently focused on these tasks:

1. use Lojban text to add statements to knowledge bases, or ask
questions about the content
2. describe data contained within knowledge bases, using Lojban text

(A triple is an instance of subject, predicate, and object. Many of
these, in combination, form a graph database that is called a
triplestore. Some people refer to these as knowledge bases.)

I chose to start with a mapping of a few brivla to URIs (RDF uses URIs
as identifiers to form statements), and then convert to and from some
queries against an RDF store.

Nothing is cast in stone yet for a URI format, or for which OWL
ontologies are to be applied. The goal is not to replace other systems
or try to do everything, but to augment existing work and allow Lojban
to play an interesting part in this experiment.

Using DBPedia, geonames, and other public linked data sets, there is
already a huge amount of data with which to work. The reason I
mentioned Wordnet, is that if a Lojban Wordnet were created, it would
allow mapping of Lojban synsets to existing data. The English Wordnet
data is already linked to many other ontologies (e.g. DBPedia, SKOS,
Library of Congress Subject Headings, music, movie, and book metadata,
to name just a few). There are billions of linked triples, and this
number is growing exponentially. See http://linkeddata.org/ and
imagine what would happen if Lojban text could be easily generated
from these data sources.

Technical details for my initial work: I am using Robin's PEG parser
to read simple brivla and convert these into Java structures, which I
then convert to statements using an RDF API, and place into Sesame (a
triplestore implementation). Using words such as "ma", it will not be
too difficult to convert some Lojban questions into simple SPARQL
queries.

There is no code yet on the jorne site. Any code is on my machine in a
very rough state. The jorne page has not been updated in several
years, and there are certainly many unmentioned new technologies and
standards that can be applied.

To answer Oren's question, I would suggest that describing the entire
Lojban vocabulary using technologies such as in the links given
(perhaps starting with a Wordnet implementation?) would bring great
benefit to the Lojban community. Besides Wordnet, SKOS is also an
excellent way to implement a Semantic-Web-friendly thesaurus.

Regards,
la iuban.

Quoting Oren <get....@gmail.com>:

> The jorne page on sourceforge [http://jorne.sourceforge.net/] doesn't
> mention OWL or appear to have any source code... is there a newer
> specification or codebase that I'm missing? The PEG parser?
>
> As for the ideas proposed on the page, I still need to be sold. There seems
> to be overlap with the W3C incubator projects for representing Wordnet in
> RDF/OWL http://www.w3.org/TR/wordnet-rdf/, and quite frankly, lojban's
> minimal and prescriptive vocabulary doesn't seem to offer much application
> here.
>
> Two separate overlapping W3C incubator projects seem to be more appropriate
> for semantic querying, Common Web Language (semantic representation)
> http://www.w3.org/2005/Incubator/cwl/XGR-cwl-20080331/ and Emotional Markup
> Language http://www.w3.org/2005/Incubator/emotion/XGR-emotionml-20081120/.
>
> Lojban, as a human language, can't offer what these robust proposals
> describe-- that is, you can't really argue that lojban is any more
> 'readable' than these languages, nor believe that it would be briefer or
> more thorough; but it may be fun to try and define the entire lojban
> vocabulary using these technologies. Or maybe that's what you meant all
> along?
>

> <http://www.w3.org/TR/wordnet-rdf/>co'o mi'e korbi

>>>> lojban+un...@googlegroups.com<lojban%2Bunsu...@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 loj...@googlegroups.com.
>>> To unsubscribe from this group, send email to

>>> lojban+un...@googlegroups.com<lojban%2Bunsu...@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 loj...@googlegroups.com.
>> To unsubscribe from this group, send email to

>> lojban+un...@googlegroups.com<lojban%2Bunsu...@googlegroups.com>
>> .

[Brian Eubanks]

I also wanted to add that this effort has no intention of trying to be
an "official" thesaurus or anything like that. I am certainly not
interested in stepping on any toes. My thoughts of implementing a SKOS
or Wordnet ontology for Lojban are only intended for the purpose of
interfacing data stores with Lojban text.

Anyone with any background in RDF or Lojban is welcome to join the
project. I particularly need help with mapping the Lojban gismu to
synsets in English and other Wordnets. That would bring immediate
benefit in being able to generate simple lojban sentences from dbpedia
and other linked data content. This part could done without any
knowledge in RDF. Drop me a line if you are interested in mapping some
gismu.

Regards,
Brian Eubanks
iuban

[Oren]

coi uiban

Sorry for not getting back to you sooner! 

[snippet A]

On Mon, Apr 19, 2010 at 12:30, Brian D. Eubanks <br...@buildsoftware.com> wrote:

The project is currently focused on these tasks:
1. use Lojban text to add statements to knowledge bases, or ask questions about the content 

2. describe data contained within knowledge bases, using Lojban text

[snippet B]

 

SKOS is also an excellent way to implement a Semantic-Web-friendly thesaurus.

 

 [snippet C]

...using technologies such as in the links given (perhaps starting with a Wordnet implementation?) would bring great benefit to the Lojban community. 

So the way I see it, there are really three separate tasks here: [A] lojban knowledge authoring and extraction, [B] describing lojban using SKOS and [C] describing Wordnet using lojban, all of which I think are brilliant and awesome.

As for task [A], knowledge authoring and extraction, I think it has obvious applications with the other two, but could stand alone: lojban is already parseable (well, you know) so there's nothing stopping us from having an online lojban submission form for entering parseable knowledge (that is, any lojban text). In fact its frighteningly similar to the recent page http://lojban.org/cgi-bin/corpus, but optimally I think there should be parser validation upon submission. Searching it for completions of queries is step two. Of the applications mentioned this one, i think, is the easiest to implement: it's just a web-based parser [submission] and search [extraction].

When I say knowledge extraction, I'm thinking something like this:

>> mi klama ma //input query

mi klama lo zarci

mi pu klama lo jarbu

... //output

Task [B], describing Lojban with SKOS, I think is slightly harder if done properly, and very valuable, as it would extend the utility of [A]. Searching for { ma danlu } could give a list of all animals, and could also search for all knowledge related to animals. 

• Start with the current TeX thesaurus from the lojban website.
• Nice lojban uris. The way things work in Lojbanistan, it seems, is that the keys to the castle are available as soon as there is proof of concept. Once there's a queryable web interface, of the lojban corpus or some translated datastores, I'm sure Robin or whoever will let www.lojban.com/valsi#gismu be used for this. I have a domain name on a shared host if there's need for development space for proof of concept.
• Immediately it's a perfect thesaurus format and so one trivial-to-implement but crucial-to-have feature is importing the latest jbovlaste xml dump for adding new gloss words as prefLabels etc.
• References to other RDF schemas, not just wordnet [http://www.w3.org/TR/wordnet-rdf/]. For example, animals can be likewise translated to http://ontologi.es/biol/ns and linked to dbpedia pages, yadda yadda. This extends the domain of part A, as you put it, exponentially: open data would be searchable in a brief and robust form. This is what lojban dreams of when it says it may someday be used to talk to machines.

Now we could have input like:

>> lo cribe cu xabju ma //where do bears live

...//returns habitat information from all dbpedia entries referenced in 'cribe'

As for task [C], describing Wordnet synsets using lojban, I think this is the hardest, not merely because of the sheer number of synsets, but because of the mandate for precision-- synsets should have unique lojban terms. Semantic granularity on WordNet is pretty small, and our mere seven thousand or so current valsi are insufficient. For the part [B] task (referring to other URIs that a single lojban word *could* describe), some degree of polysemy/vagueness is fine, but for the task of describing wordnet, I think the best implementation has a one-to-one correspondence to lojban words.

This obviously entails a huge number of ad-hoc lujvo/tanru (ideally) or fi'uvla (suboptimal) that need to be created for similar shades of related synsets, or just technical or cultural words that have no lojban equivalent or approximate. I envision this only as feasible in a wiki-like, folksonomy web frontend where multiple people can help assign new lujvo to unassigned synsets. A great byproduct of this would be critical examination of the shortcomings of current gismu, and possibly accelerated specification of vague/poorly-defined terms and newly coined lojban terms.

---intermission---

I have a little proposal to distinguish these three tasks as I have described them ([A],[B], and [C]). While they are all part of the same project, I think they each play functionally distinct roles; namely a human portal, an extendable description, and the holy grail of lojban dictionaries. My proposal is that these three tasks be called jorne, sejorne and tejorne respectively. jorne is still the name of the whole idea (since the other two work through or enhance it), and

1) the 'connect' {lo jorne} refers to the user front end and basic input/query portion 

2) the 'things-connected' {lo se jorne} refers to the linked searchable/translatable ontologies/schema

3) the 'connection types' {lo te jorne} refers to the clear definition of synsets found in wordnet using lojban

Or, in laymans terms, a web front-end, a thesaurus and a dictionary.

Additionally, while the first two may only be of particular interest to lojbanists, I think the third may have even greater implications as an extension to Wordnet since it can do something Wordnet does not attempt to do: provide cardinality information. That is, lets say we want to use Wordnet to annotate a text unambiguously: that's totally possible. But if we wanted to then search that text (say, looking for query completions) theres no way to explicitly mark what lexeme falls in what argument number for a multi-argument phrase. Lojban, however, makes every bridi immediately accessible as a series of one or more triples for each sumti. Of course, this application is light-years off and might just be crazytalk. But that's why I would keep description of wordnet and description of lojban as two distinct objectives.

co'o mi'e korbi

btw, are you located in the united states by any chance? you might be interested in the North American Summer School in Logic, Language and Information. 

[Brian D. Eubanks]

coi korbi

This was a busy week for me, so now it was my turn to delay in getting
back to you. We are pretty much thinking along the same lines, and
your description codified the issues quite well.

Interesting idea to call the parts jorne, sejorne, and tejorne. A web
front-end or web service would be a great first step. I am very close
to setting up a simple lojban text-to-XML parser service. Getting
triples out of the XML would be pretty easy, although the parse tree
coming out of RATS is extremely deep.

I see two immediate use cases for the jorne web service. The first is
a public parser REST API that could be used for Lojban mashups. Lojban
in, XML out. Alternate output format of the web service would be RDF,
as either RDF/XML or N3 serialization. I do have a jorne.org hosted
server, and can have it run the first implementation of the API.

The second use case would be the web service that stores
lojban-derived triples, and allows simple queries in SPARQL and
eventually Lojban. These could be the same API but different features
of it.

I am on the East Coast of the U.S., near Washington, D.C.. The Summer
School would be fun to attend. I do plan to attend the Semantic
Technologies Conference during June, in San Francisco.

More later.

mu'o mi'e iuban

> - Start with the current TeX thesaurus from the lojban website.
> - Nice lojban uris. The way things work in Lojbanistan, it seems, is that

> the keys to the castle are available as soon as there is proof of concept.
> Once there's a queryable web interface, of the lojban corpus or some
> translated datastores, I'm sure Robin or whoever will let
> www.lojban.com/valsi#gismu be used for this. I have a domain name on a
> shared host if there's need for development space for proof of concept.

> - Immediately it's a perfect thesaurus format and so one

> trivial-to-implement but crucial-to-have feature is importing the latest
> jbovlaste xml dump for adding new gloss words as prefLabels etc.

> - References to other RDF schemas, not just wordnet [

> Information <http://www.indiana.edu/~nasslli/overview.html>.

>>>>>> <lojban%2Bunsu...@googlegroups.com<lojban%252Buns...@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 loj...@googlegroups.com.
>>>>> To unsubscribe from this group, send email to
>>>>> lojban+un...@googlegroups.com<lojban%2Bunsu...@googlegroups.com>

>>>>> <lojban%2Bunsu...@googlegroups.com<lojban%252Buns...@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 loj...@googlegroups.com.
>>>> To unsubscribe from this group, send email to
>>>> lojban+un...@googlegroups.com<lojban%2Bunsu...@googlegroups.com>

>>>> <lojban%2Bunsu...@googlegroups.com<lojban%252Buns...@googlegroups.com>