|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Interface Summary | |
---|---|
Cloneable | Indicates that it is legal to make a field-for-field copy of instances of implementing classes. |
GenericName | Base interface for scoped and local name structure for type and attribute name in the context of name spaces. |
InternationalString | A string that has been internationalized into several locales. |
LocalName | Identifier within a name space for a local object. |
MemberName | The name to identify a member of a record. |
NameFactory | Factory for generic names and international strings. |
NameSpace | A collection of 0 or more generic names. |
ProgressListener | Monitor the progress of some lengthly operation, and allows cancelation. |
Record | A list of logically related elements as (name, value) pairs in a dictionary. |
RecordSchema | A collection of record types. |
RecordType | The type definition of a record. |
ScopedName | A composite of a local name (as head) for locating another name space, and a generic name (as tail) valid in that name space. |
TypeName | The name of an attribute type. |
Class Summary | |
---|---|
CodeList<E extends CodeList<E>> | Base class for all code lists. |
SimpleEnumerationType<E extends SimpleEnumerationType<E>> | Class that implements simple, type safe enumerations in Java. |
UnlimitedInteger | An integer with associated infinite flag. |
Exception Summary | |
---|---|
NoSuchEnumerationException | Exception that is thrown when an invalid enumeration lookup is performed
in the SimpleEnumerationType class. |
A set of utilities classes and interfaces for OpenGIS interfaces. This package defines some stereotypes used in OGC's UML diagrams.
The job of a "name" in the context of ISO 19103 is to associate that name
with an Object
. Examples given are objects: which form namespaces
for their attributes, and Schema: which form namespaces for their components.
A straightforward and natural use of the namespace structure defined in 19103 is the translation
of given names into specific storage formats. XML has different naming rules than shapefiles,
and both are different than NetCDF. This common framework can easily be harnessed to impose
constraints specific to a particular application without requiring that a separate implementation
of namespaces be provided for each format.
Records and Schemas are similar to a struct
in C/C++, a table in SQL,
a RECORD
in Pascal, or an attribute-only class in Java if it were stripped of all notions
of inheritance. They are organized into named collections called Schemas. Both records and schemas
behave as dictionaries for their members and are similar to "packages" in Java.
|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |