|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
This interface describes a base name associated with a topic.
A base name is the base form of a topic name; it is always a string.
Base names can be scoped, meaning that the name is valid only
within certain constraints. A popular way of using scoped base
names is to define natural languages as scopes and to thereby be
able to name a topic in various languages.
One of the trickier implications of this is the Topic Naming
Constraint, stating that if in a topic map context there are
two topics with identical names in identical scopes, they must be
merged. Basic names can also contain Variants, which need not necessarily
represent strings.
Scopes and variants can be addressed by implementing classes
by using the methods of the parent ScopedObject
and
VariantContainer
interfaces, respectively.
For more information about topic names, see the XTM 1.0 Specification..
Method Summary | |
java.lang.String |
getData()
Returns the data string for this name. |
Topic |
getParent()
Returns the Topic object which contains this BaseName. |
void |
setData(java.lang.String data)
Sets the data string for this name. |
Methods inherited from interface org.tm4j.topicmap.ScopedObject |
addTheme, dispose, getScope, inScope, inScope, removeTheme, setScope |
Methods inherited from interface org.tm4j.topicmap.VariantContainer |
addVariant, createVariant, getVariants, setVariants |
Method Detail |
public java.lang.String getData()
public void setData(java.lang.String data) throws java.beans.PropertyVetoException
data
- the new data string.
java.beans.PropertyVetoException
- If a listener vetos the updatepublic Topic getParent()
Topic
.
|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |