FDS
2.0
  • 1. Intro
  • 2. FDS communication model
    • 2.1. Common Definitions
    • 2.2. Conventions
    • 2.3. Object models
    • 2.4. Information Management through the Web API (Pull Model)
    • 2.5. Information Management through Publish/Subscribe (Push Model)
    • 2.6. Security model
  • 3. By equipment type
  • 4. By space type
  • 5. Reference
FDS
  • 2. FDS Communication models
  • View page source

2. FDS Communication models

  • 2.1. Common Definitions
    • 2.1.1. Entity
    • 2.1.2. Actors
    • 2.1.3. Use case example
  • 2.2. Conventions
    • 2.2.1. Naming Conventions
    • 2.2.2. Versioning
    • 2.2.3. Formatting
    • 2.2.4. Data Types
    • 2.2.5. Floating point representation
    • 2.2.6. Date and Time
    • 2.2.7. Percentage
    • 2.2.8. Geolocation
    • 2.2.9. Images
    • 2.2.10. Status codes
  • 2.3. Object models
    • 2.3.1. Definitions
    • 2.3.2. FDS compliance requirements
    • 2.3.3. Use case example
  • 2.4. Information Management through the Web API (Pull Model)
    • 2.4.1. Devices Information
    • 2.4.2. Physical environment
    • 2.4.3. Events Information
    • 2.4.4. Grouping and logical organization (Tags)
  • 2.5. Information Management through Publish/Subscribe (Push Model)
    • 2.5.1. Definitions
    • 2.5.2. Supported technologies
    • 2.5.3. FDS compliance requirements
    • 2.5.4. Workflow
    • 2.5.5. Use case example
  • 2.6. Security model
    • 2.6.1. Definitions
    • 2.6.2. Security Threats
    • 2.6.3. Resources
    • 2.6.4. FDS compliance requirements
    • 2.6.5. Workflow
    • 2.6.6. Use case example
Previous Next

© Copyright 2021, FDS.

Built with Sphinx using a theme provided by Read the Docs.