SEDRIS Data Dictionary ------------------------------------------------------------------------------- Class Name: Absolute Time Interval Definition: An instance of this DRM class represents an interval of time defined by an absolute (GMT) start time, specified by the component, and a duration, specified by the fields of the itself. provides - a means to specify a time interval in terms of absolute time (GMT) for CSDGM-compliant metadata, and - a general-purpose mechanism for describing intervals specified in terms of absolute (GMT) time. Primary Page in DRM Diagram: 20 Example: 1. Consider a SEDRIS transmittal for which the data provider is to specify the time period for which that transmittal is to be considered valid. To specify this information, the of the transmittal has an component for which time_significance is set to SE_TIME_SIGNIFICANCE_PERIOD_OF_CONTENT. The stop time specified by the can be considered to be an "expiration date". FAQS: None. Superclass: Time Interval Constraints: Legal Time Ranges Time Dependency Time Interval Calculation Composed of (two-way) one Absolute Time Point instance Component of (two-way)(inherited) zero or more Environment Root instances zero or more Time Constraints Data instances zero or one Transmittal Root instance zero or more Month instances zero or more Season instances zero or more Sound Instance instances zero or more Source instances Inherited Field Elements: SE_Time_Significance time_significance; /* * This indicates the significance of the time information. */ Field Elements: SE_Integer delta_days; /* * This is the number of days since the start of the * . * * See constraints on this class for cases where this may be * negative. */ SE_Byte_Unsigned delta_hours; /* * After delta_days has been taken into account, this is the * number of hours since the start of the , * and therefore shall be a value between 0 and 23. */ SE_Byte_Unsigned delta_minutes; /* * After delta_days and delta_hours have been taken into account, * this is the number of minutes since the start of the * , and therefore shall be a value between * 0 and 59. */ SE_Long_Float delta_seconds; /* * After delta_days, delta_hours, and delta_minutes have been * taken into account, this is the number of seconds since the * start of the , and therefore shall be * a value between 0.0 and 59.0. * * Fractions provide higher accuracy if needed, e.g. milliseconds. */ ------------------------------------------------------------------------------- Class Name: Absolute Time Point Definition: An instance of this DRM class is used to specify an absolute time (that is, Greenwich Mean Time (GMT), which is not relative to some other point in time). provides - a means to specify an absolute time (GMT) for CSDGM-compliant metadata, and - a general-purpose mechanism for describing points in absolute (GMT) time. Primary Page in DRM Diagram: 20 Example: 1. Consider a SEDRIS transmittal constructed from a historical database, in which the time at which an event happened is recorded as Oct 3 17:56:47 GMT 1994. In the SEDRIS transmittal, this information is specified by an instance with time_significance = SE_TIME_SIGNIFICANCE_OCCURRENCE, as follows. time_significance = SE_TIME_SIGNIFICANCE_OCCURRENCE year = 1994 month = SE_MONTH_OCTOBER day = 3 hour = 17 minutes = 56 seconds = 47.0 2. Consider a SEDRIS transmittal for which the data provider wishes to represent the date and time when the transmittal was created - in this example, Mar 23 15:18:33 GMT 2003. In this case, the data provider would create an instance with time_significance = SE_TIME_SIGNIFICANCE_CREATION_DATE and the other field values set appropriately, as follows. time_significance = SE_TIME_SIGNIFICANCE_CREATION_DATE year = 2003 month = SE_MONTH_MARCH day = 23 hour = 15 minutes = 18 seconds = 33.0 This instance would then be attached as a component of the transmittal's . 3. The date and time of observations. FAQS: Q. How may a data provider indicate that the time information in an instance is not dependent on the year? A. Setting year = -1 indicates this. Please note that this means that an actual date of 1 BCE (before common era) cannot be used. (It is anticipated that the only time a BCE date would be desired would be for astronomical Julian dates). Q. How may a data provider indicate that the time information in an instance is not dependent on the month? A. Setting month = SE_MONTH_ANY indicates this. Q. How may a data provider indicate that the time information in an instance is not dependent on the day? A. Setting day = -1 indicates this. Q. How may a data provider indicate that the hour, minutes, and seconds fields are not applicable, that is, that the instance specifies only a date? A. Setting hour = -1, minutes = -1, and/or seconds = -1 indicates that they are not applicable and are to be ignored. Superclass: Time Point Constraints: Legal Time Ranges Component of (two-way)(inherited) zero or more Environment Root instances zero or more Time Constraints Data instances zero or one Transmittal Root instance Component of (two-way) zero or more Absolute Time Interval instances zero or more Citation instances zero or more Process instances zero or more Relative Time Interval instances zero or more Relative Time Point instances Inherited Field Elements: SE_Time_Significance time_significance; /* * This indicates the significance of the time information. */ Field Elements: SE_Short_Integer year; SE_Month month; SE_Short_Integer day; SE_Byte hour; /* * Use 24 hour clock for hour. The value shall be between -1 and 23, * where a value of -1 indicates not applicable. */ SE_Byte minutes; /* * The value shall be between -1 and 59, * where a value of -1 indicates not applicable. */ SE_Long_Float seconds; /* * Fractions provide higher accuracy if needed, e.g. milliseconds. * -1 is the only negative value, and indicates not applicable. */ ------------------------------------------------------------------------------- Class Name: Access Definition: An instance of this DRM class specifies the security classification and any access and/or usage constraints for its containing SEDRIS object, provided in a CSDGM-compliant form. Primary Page in DRM Diagram: 1 Secondary Pages in DRM Diagram: 2 3 6 8 10 14 19 21 22 23 Example: 1. Given a that has restricted access (no access by non-U.S. citizens) and is for official use only, its information might be access_constraints = "NOFORN"; use_constraints = "FOUO"; security.system = "United States Department of Defense"; security.classification = "SECRET"; security.handling = "Downgrade on 31 Dec 1999"; FAQS: Q. What is the purpose of this class? A. This class supports the creation of SEDRIS transmittals that contain classified or sensitive data. Q. How is the security classification of a SEDRIS object related to the security classifications of its component objects, or to the security classification of its containing object? A. In general, the rules for security classification metadata for the SEDRIS objects within a transmittal are the same as the rules for security classification markings of the paragraphs and sections within a hierarchically structured classified document. The security classification of an object shall be at least as high as the highest of the security classifications of its components, and may be higher if the aggregation of the components allows additional information to be inferred. Therefore, the security classification of an object shall be no higher than the security classification of its containing object. Unclassified objects need not have an component, unless they are unclassified components of a classified containing object. Superclass: SEDRIS Abstract Base Constraints: Mandatory Metadata Component of (two-way) zero or more Attribute Set instances zero or more Attribute Set Table instances zero or more Attribute Set Table Group instances zero or more Colour Table instances zero or more Colour Table Group instances zero or more Data Table instances zero or more Environment Root instances zero or more Feature instances zero or more Feature Model instances zero or more Geometry Hierarchy instances zero or more Geometry Model instances zero or more Image instances zero or more Library instances zero or more Model instances zero or more Sound instances zero or more Symbol instances zero or one Transmittal Root instance Field Elements: SE_String access_constraints; /* * This specifies the restrictions on access to the given * data object (Optional). */ SE_String use_constraints; /* * This specifies the restrictions on use of the given * data object (Optional). */ SE_Security_Info security; /* * This specifies the security classification for the given * data object (Mandatory) */ ------------------------------------------------------------------------------- Class Name: AEC Location 3D Definition: An instance of this DRM class specifies a coordinate within the Augmented Equidistant Cylindrical (AEC) 3D Spatial Reference Frame (SRF). See [I18026] for a complete definition. Primary Page in DRM Diagram: 15 Example: 1. Consider a SEDRIS transmittal constructed from a MultiGen OpenFlight database. The transmittal contains an instance ER, the ORM of which is MultiGen Flat Earth, such that the srf_parameters field of ER is specified in Augmented Equidistant Cylindrical with the Multigen "flat Earth" horizontal and vertical datums, SRM_HDATUM_SPHERICAL_MFE and SRM_VDATUM_SPHERICAL_MFE. An within this spatial reference frame might be x = 30.0, y = 50.0, z = 100.0. FAQS: Q. Where can users obtain further information on AEC? A. See the Spatial Reference Model (SRM) for additional details. Superclass: Location 3D Constraints: Environment Root Spatial Reference Frame Image Anchor Spatial Reference Frame Model Spatial Reference Frame Component of (two-way)(inherited) zero or more Arc instances zero or more Base Reference Vector instances zero or more Directional Light Behaviour instances zero or one Distance Level Of Detail Data instance zero or more Ellipse instances zero or more Elliptic Cylinder instances zero or more Feature Edge instances zero or one Feature Node instance zero or more Image Anchor instances zero or more Label instances zero or one Location Table instance zero or more Morph Point instances zero or more Perimeter Data instances zero or more Point Geometry instances zero or more Property Grid Hook Point instances zero or one Reference Origin instance zero or more Spatial Domain instances zero or more Spatial Index Related Feature Topology instances zero or more Spatial Index Related Features instances zero or more Spatial Index Related Geometry instances zero or more Spatial Index Related Geometry Topology instances zero or more Tack Point instances zero or more Vertex instances zero or more Vertex With Component Indices instances zero or more World 3x3 instances zero or more World Transformation instances zero or one Attachment Point instance zero or more Base Positional Light instances zero or more Centre Of Buoyancy instances zero or more Centre Of Mass instances zero or more Centre Of Pressure instances zero or one Contact Point instance zero or more Separating Plane instances zero or more Sound Instance instances zero or more Stamp Behaviour instances zero or more Volume instances zero or more Volume Level Of Detail Data instances zero or more Volume Light Behaviour instances Field Elements: SRM_AEC_Coordinate_3D coordinate; ------------------------------------------------------------------------------- Abstract Class Name: Aggregate Feature Definition: An instance of this DRM class specifies a collection of and/or instances, organized according to some organizing principle specific to the particular subclass of being considered. For most subclasses of , each individual branch of the aggregation is explicitly identified by a distinct link object. The various subclasses provide different mechanisms for organizing instances, which include: ALTERNATE HIERARCHY: Each branch is a with a different instance, representing a different way of organizing the same underlying collection of instances. CLASSIFICATION: Each branch is a with a different instance, representing a different thematic layer, or a different classification of instances (e.g., roads, railroads) within a single thematic layer. LEVEL_OF_DETAIL: Each branch is a with a distinct (but possibly overlapping), instance, representing an alternative that is to be used at a specified level of detail. OCT_TREE: The represents an octree, where each branch is a representing an octant within the octree, as identified by its instance. PERIMETER: Each branch is a that is located within a different cell of an irregular spatial index, as defined by its instance. QUAD_TREE: The represents a quadtree, in which each branch is a representing a quadrant within the quadtree, as identified by its instance. SPATIAL_INDEX: The represents a regularly spaced spatial index grid, in which each branch is instance representing a different cell within the spatial index. STATE: The represents something that can take on different state values for a specified EDCS Attribute Code (the state_tag, which shall have the "state-related" property). Each branch is a instance with a different instance, representing an alternative that shall be used to represent the when it takes on the specified state value. TIME: The represents something that has different representations for different time periods, so that each branch is a instance with a distinct (though possibly overlapping)