Skip to end of metadata
Go to start of metadata

The data definition in a specification are usually provided as a "Data Dictionary" or "XML Schema". This information is where we find details for our javadocs.

Example ISO "Data Dictionary"

B.2.8.1 General

  • UML model shown in Figure 1.10

233.

 

Name / Roll Name:

MD_FeatureCatalogDescription

Short Name:

FetCatDesc

Definition:

information identifying the feature catalog or the conceptual schema

Obligation / Condition:

from reference

Maximum Occurance:

from reference

Data type:

Specified Class (MD_ContentInformation)

Domain:

Lines 234-238

234.

 

Name / Roll Name:

complianceCode

Short Name:

compCode

Definition:

indication of whether or not the cited feature catalogue complies with ISO 19110

Obligation / Condition:

Optional

Maximum Occurance:

1

Data type:

Boolean

Domain:

0-not compliant
1-compliant

239.

 

Name / Roll Name:

MD_CoverageDescription

Short Name:

CovDesc

Definition:

information about the content of a grid data cell

Obligation / Condition:

from reference

Maximum Occurance:

from reference

Data type:

Specified Class (MD_Content Information)

Domain:

Lines 240-242

241.

 

Name / Roll Name:

contentType

Short Name:

contentTyp

Definition:

Manditory

Obligation / Condition:

1

Maximum Occurance:

N

Data type:

Class

Domain:

MD_CoverageContentTypeCode<<CodeList>> (B.5.12)

Armed with the data dictionary we can now update the javadoc descriptions.

Labels
  • None