Names and Namespaces
The job of a "name" in the context of ISO 19103 is to associate that name
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
Records and Schemas are similar to a
struct in C/C++, a table in SQL,
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.
Interface Summary Interface Description CloneableIndicates that it is legal to make a field-for-field copy of instances of implementing classes. GenericNameA sequence of identifiers rooted within the context of a namespace. InternationalStringA string that has been internationalized into several locales. LocalNameIdentifier within a name space for a local object. MemberNameThe name to identify a member of a record. NameFactory NameSpaceA domain in which names given by character strings are defined. ProgressListenerMonitor the progress of some lengthly operation, and allows cancelation. RecordA list of logically related elements as (name, value) pairs in a dictionary. RecordSchemaA collection of record types. RecordTypeThe type definition of a record. ScopedName TypeNameThe name of an attribute type.
Class Summary Class Description CodeList<E extends CodeList<E>>Base class for all code lists. UnlimitedIntegerAn integer with associated infinite flag.