TDL The TDL is a reliable controlled data repository. The following sections define requirements for the TDL. Data The TDL database shall maintain all FLM-X data. The database shall also maintain information about TDL participants, access control information and other administrative data. FLM-X data is described in more detail in [ML-FLMX-DATA]. FLM-X data and format is subject to revision through the ISDCF (). Data Sources The TDL has several data sources: Device manufacturers, Exhibitors, Deployment Entities, Integrators, Service Providers (interacting with Exhibitors), regional authorities and Support. The TDL shall accept data from these data sources as constrained by access rights. Future sources may be defined in the future and should be accessible using the same interfaces. Facility Data FLM Data The TDL shall store all FLM messages, plus additional administrative data including at least when and how the data arrived at the system (e.g., via message, web or REST interfaces). The mandatory subset of the FLM-X data will be defined as part of this Project. It is expected that many of the fields in the FLM-X message will be optional. In addition to FLM message, the following data will be maintained: Date and time that data arrives or is entered at TDL. Note that IssueDate from the structure precedence because messages may be delayed Method of update: email, web, REST, etc. Authority (e.g., username) Audit data any data necessary to validate the integrity of the other data – Annotation Where resolution of problems is performed, additional information can – supplement the FLM-X data. and Log Information shall be kept concerning the history of the facility data including errors found and potentially corrected (but not verified) by distributors. Participant Data Information shall be maintained on participants, including exhibitors, device manufacturers, studios, service providers, distributors, deployment entities, integrators and their representatives.
TDL The TDL is a reliable controlled data repository. The following sections define requirements for the TDL. Data The TDL database shall maintain all FLM-X data. The database shall also maintain information about TDL participants, access control information and other administrative data. FLM-X data is described in more detail in [ML-FLMX-DATA]. FLM-X data and format is subject to revision through the ISDCF (). Data Sources The TDL has several data sources: Device manufacturers, Exhibitors, Deployment Entities, Integrators, Service Providers (interacting with Exhibitors), regional authorities and Support. The TDL shall accept data from these data sources as constrained by access rights. Future sources may be defined in the future and should be accessible using the same interfaces. Facility Data FLM Data The TDL shall store all FLM messages, plus additional administrative data including at least when and how the data arrived at the system (e.g., via message, web or REST interfaces). The mandatory subset of the FLM-X data will be defined as part of this Project. It is expected that many of the fields in the FLM-X message will be optional. In addition to FLM message, the following data will be maintained: Date and time that data arrives or is entered at TDL. Note that IssueDate from the structure precedence because messages may be delayed Method of update: email, web, REST, etc. Authority (e.g., username) Audit data – any data necessary to validate the integrity of the other data Annotation – Where resolution of problems is performed, additional information can supplement the FLM-X data. and Log Information shall be kept concerning the history of the facility data including errors found and potentially corrected (but not verified) by distributors. Participant Data Information shall be maintained on participants, including exhibitors, device manufacturers, studios, service providers, distributors, deployment entities, integrators and their representatives.