96 | | TBD |
| 96 | === Integrating Annotation Text Concepts into the FDO API === |
| 97 | |
| 98 | In order to support Annotation Text and the concepts outlined in the sections above, the object and metadata relationships defined by the OGC Simple Feature Access Specification will be incorporated into the FDO API as outlined in the sections below. |
| 99 | |
| 100 | ==== Annotation Text Definitions as an FDO Property Definition ==== |
| 101 | |
| 102 | Annotation Text and its logical metadata will be creatable, modifiable and describable via the FDO API schema. Annotation Text will be defined as properties on FDO Feature Classes and be exposed in the same manner as Geometry, Raster and Associations, via an FDO property definition class that derives from !FdoPropertyDefinition. In this manner, class !FdoAnnotationPropertyDefinition will be added to the API and will contain the definition of the schema, classes and properties that define the location of the Annotation components. These elements are the logical properties that are needed to store the annotation text value, envelope, leader line, location and text attributes. The schema, classes and properties identified by these metadata properties will in turn be accessible through their own FDO schema definitions. |
| 103 | |
| 104 | ===== Starting from an Existing Physical Schema ===== |
| 105 | |
| 106 | Let us use the following physical schema as a starting point for further discussion. In this example a Road table is used to capture the Location, Name and Width of road objects in a city. Associated to the Road table is a !RoadAnnotation table that contains textual labels that describe the road. A Road object can be associated to 0…n !RoadAnnotation objects. |
| 107 | |