This is my (arj's) proposal for new Jbovlaste guidelines. Feel free to edit directly, or send me comments or suggestions.
The aim of these guidelines is to enable editors with different styles to collaborate on creating a dictionary database that is as consistent and high-quality as possible.
Unless otherwise specified, "English" refers to any of the meta languages that Jbovlaste uses. (In the interface, these are called "natural languages", even though some constructed languages, such as Klingon and Loglan are included).
When preparing dictionaries for natural languages, the usual problem is which of the millions of words are important enough that they need to have a definition. Lojban's vocabulary is much smaller than that, but we do have limited manpower with which to write definitions. Some words are more important than others, and should be prioritized.
That being said, most of us work on Jbovlaste because it is fun. If we didn't spend some time once in a while with fun distractions, we would get demotivated, and the important things would never get done.
All definitions end with a period.
Definitions of brivla must include a place structure. In fact, almost all definitions of a brivla consist of nothing but a place structure definition.
The best way to find out what the place structure of a brivla is, is to base it on usage. Unfortunately, there is almost never enough usage data to gain any kind of insight on the places beyond x1.
If available, existing Noralujv entries may be used as a template. These entries usually reflect best practices, but be wary of clerical errors.
Fu'ivla place structures should have plain numbered arguments: x_1 ... x_n.
Lujvo place structures should have arguments that point to its component gismu. The symbol for the arguments should be the shortest possible abbreviation of the gismu such that no ambiguity occurs. For instance, if the lujvo is based on bloti, and girzu, it is okay to just use b and g. If the lujvo is based on badna and bancu, however, bad and ban must be used.
The arguments must be in ascending order and without skipping any argument. If it is necessary to reorder the arguments in the definition to make it flow more smoothly, all places must be explicitly numbered with x_1 - x_n.
As a conssquence, if a component gismu begins with x, at least two letters must be used in the argument abbreviation, so that it can't be misunderstood as referring to a numbered place.
Parentheses usually have the same meaning as in ordinary language.
You may specify which kind of abstraction is expected in a particular place by adding the abstractor (of selma'o NU) after the term in question.
Some gismu definitions use square brackets. Since their meaning is not completely understood, they should be avoided in new definitions.
A solidus ('/') between different words or phrases signifies inclusive OR. This might best be illustrated by an example.
rodbo'e: $brode_1$ is a foo/bar/quux of $broda_1$.
This means that for something to be rodbo'e, it needs to be either foo, bar, or quux, or any combination thereof. If it is neither foo, bar or quux, it is not a rodbo'e.
The wording of a gismu definition in English is baselined and must not be modified.
The notes field is logically organised in several parts. Not all parts should be present in all entries, but they should be in the same order.
The notes field should not contain any information that is or could be automatically generated. In particular, the notes field for a lujvo should not explain which gismu it is composed of (but it may point to those gismu in the cross-references).
If the place structure of a lujvo departs significantly from jvojva, this should be explained. Typically this means that a place has been omitted because it contains little useful information.
Incorrect
Correct
Cross-references are signified by "Cf." (an abbreviation for "confer", which means "see"), and one or more words enclosed in curly brackets, separated by a command a space, and ends with a period.
Example
Examples should only occur in example fields, not anywhere else. Examples should illustrate the meaning and/or usage of the word in question. Genuine examples are preferred over invented examples.
The purpose of keywords is to serve as a natural-language index to the Lojban dictionary. The Jbovlaste infrastructure does not work well as a basis for an English-to-Lojban dictionary, and this is in fact undesirable. To the extent that Lojban and English carves reality in different ways in terms of the vocabulary, the selection of English keywords should reflect this.
Keywords should be given in their citation form. They should not be inflected, or have particles attached to them.
Incorrect
Correct
Key "words" may have multiple words, and having a multi-word expression may in some cases be the best solution. But such keywords must always be a distinct lexical item, and it should not be too long.
Incorrect
Correct
In exceptional cases, part of a keyword can be fronted with a comma, to ease searching.
Example
The sense field of a keyword should be used if an English speaker (with no knowledge of Lojban) perceives a word to have multiple distinct meanings.
Multiple senses of a word should not be used to indicate a semantic distinction that occurs only in Lojban. A keyword must never be split into multiple senses simply to ensure that two or more Lojban synonyms (or near-synonyms) are included in the English part of the dictionary.
Incorrect
Correct
The sub-sense of a keyword (the part in the parentheses) should preferably be an exact equivalent (synonym), with which the keyword could be replaced in running text without change in meaning. A short phrase may be used, if necessary.
If a usable synonym cannot be found, the second-best solution is to use an adjective, prepositional phrase or adverbial that is meant to be read as part of the keyword.
Grammatical terms (noun, verb, adjective etc.) must never be used as a sub-sense description. The only exception to this is the term "attitudinal", since linking to attitudinals from the English index would otherwise be too difficult.
Terms that specify which field a jargon term belongs to (mathematics, botany, etc.) are likewise to be avoided.
Incorrect
Correct