LogoLogo
Give FeedbackGovStack Home
Development
Development
  • GovStack
  • Contributing
  • Architecture and Nonfunctional Requirements
    • 2 Introduction
    • 3 GovStack Architecture
    • 4 Building Block Design Principles and Considerations
    • 5 Cross-Cutting Requirements
    • 6 Onboarding Products
    • 7 Standards
    • 8 UI Switching and Handover
    • 9 Other Resources
  • Security Requirements
    • 2 Description
    • 3 Terminology
    • 4 Security Management
    • 5 Cross-Cutting Requirements
    • 6 Standards
    • 7 Authorization Services
    • 8 Additional Security Modules
    • 9 Other Resources
  • Digital Sovereignty - Cloud Infrastructure
    • Abstract
    • Digital sovereign cloud technology
    • Digital Sovereignty considerations
    • Architectural graphics
  • GovStack UI/UX Guidelines
    • 1 Version History
    • 2 Description
    • 3 Service design good practice guidelines
      • 3.1 User-centred design
        • 3.1.1.1 Understand needs and requirements
        • 3.1.1.2 Involve others in the design process
        • 3.1.2.1 Test with users
        • 3.1.3.1 Share findings
        • 3.1.3.2 Monitor performance
          • 3.1.3.3 Set up analytics
      • 3.2 Accessibility and inclusion
        • 3.2.1.1 Test for accessibility
        • 3.2.2.1 Involve a diverse user group in the design
        • 3.2.2.2 Support multiple languages
        • 3.2.2.3 Foster a culture of inclusion
      • 3.3 Consistency
        • 3.3.1.1 Use simple language
        • 3.3.2.1 Implement a consistent style guide
        • 3.3.2.2 Use design patterns
        • 3.3.2.3 Use a frontend framework
        • 3.3.3.1 Interoperability
        • 3.3.3.2 Use integrations
        • 3.3.4.1 Work in the open
      • 3.4 Technology choices
        • 3.4.1.1 Choose the right level of security
        • 3.4.1.2 Design for privacy
        • 3.4.2.1 Optimise load times
        • 3.4.2.2 Account for connectivity issues
        • 3.4.3.1 Test across platforms
        • 3.4.3.2 Design cross-channel
    • 4 Design patterns
      • 4.1 Service patterns
      • 4.2 User flows
        • 4.2.1 Register
        • 4.2.2 Authenticate
        • 4.2.3 Asking users for feedback
        • 4.2.4 Find a service
        • 4.2.5 Check a users eligibility
        • 4.2.6 Make an application
      • 4.3 Page templates
        • 4.3.1 Feedback
        • 4.3.2 Perception survey
        • 4.3.3 Satisfaction
        • 4.3.4 Before you start
        • 4.3.5 Service sheet
        • 4.3.6 Asking users for consent
        • 4.3.7 Task list
        • 4.3.8 Asking users for information
        • 4.3.9 Check answers
        • 4.3.10 Outcome
    • 5 Use-case examples
    • 6 References
    • 7 Other Resources
  • Building Blocks
    • About Building Blocks
    • Consent
    • Digital Registries
    • E-Marketplace
    • E-Signature
    • Geographic Information System (GIS)
    • Identity
    • Information Mediation
    • Messaging
    • Payments
    • Registration
    • Scheduler
    • Workflow
  • Cloud Infrastructure
  • Use Cases
    • Reference Use Cases
  • Public Administration Ecosystem Reference Architecture (PAERA)
    • PAERA
  • Tools
    • Sandbox
  • Release Notes
    • 23Q4
Powered by GitBook

Apache-2.0 license

On this page
  • 7.1 Unicode
  • 7.2 ISO8601/UTC
  • 7.3 JSON
  • 7.4 JSON Schema
  • 7.5 REST
  • 7.6 OpenAPI (AKA Swagger)
  • 7.7 Docker/Docker Compose/OCI Containers
  • 7.8 QR code

Was this helpful?

  1. Architecture and Nonfunctional Requirements

7 Standards

Previous6 Onboarding ProductsNext8 UI Switching and Handover

Last updated 9 months ago

Was this helpful?

The following standards MUST be used in the development of any Building Block. Adhering to common standards as listed below promotes interoperability and facilitates efficient data transfer between Building Blocks.

7.1 Unicode

Used for encoding text

7.2 ISO8601/UTC

Used for dates and timestamps

7.3 JSON

Used for exchanging data

7.4 JSON Schema

7.5 REST

Used for implementing APIs

7.6 OpenAPI (AKA Swagger)

7.7 Docker/Docker Compose/OCI Containers

7.8 QR code

Must be generated with the ISO/IEC 18004:2015 standard

Used for specifying data models. Note that OpenAPI 3.1 has full support for JSON Schema

Used for specifying and documenting APIs. Use latest version: Note that OpenAPI 3.1 supports inline JSONSchema for model definitions

Used for packaging building block components for deployment

http://json-schema.org/
https://swagger.io/specification/
https://en.wikipedia.org/wiki/Docker_(software)
https://www.docker.com/resources/what-container
https://en.wikipedia.org/wiki/Unicode
https://en.wikipedia.org/wiki/ISO_8601#Coordinated_Universal_Time_(UTC)
JSON
Representational state transferWikipedia
Logo
Logo