Skip to content

Latest commit

 

History

History
110 lines (59 loc) · 2.84 KB

use-case-template.md

File metadata and controls

110 lines (59 loc) · 2.84 KB
Raw

Title:

Submitter(s):

Reviewer(s):

Tracker Issue ID:

Category:

<please put "horizontal" or "vertical" here>

Class:

Status:

Target Users

<List all stakeholders that are involved in the use case from the following list:

  • device owners
  • device user
  • cloud provider
  • service provider
  • device manufacturer
  • gateway manufacturer
  • network operator (potentially transparent for WoT use cases)
  • identity provider
  • directory service operator>

Motivation:

Expected Devices:

<List the target devices, e.g. as a sensor, solar panel, air conditioner>

Expected Data:

<List the type of expected data, e.g. weather and climate data, medical conditions, machine sensors, vehicle data>

Dependencies - Affected WoT deliverables and/or work items:

Description:

Variants:

<Describe possible use case variants, if applicable>

Security Considerations:

<Describe any issues related to security; if there are none, say "none" and justify>

Privacy Considerations:

<Describe any issues related to privacy; if there are none, say "none" and justify>

Accessibility Considerations:

<Describe any issues related to accessibility; if there are none, say "none" and justify>

Internationalisation (i18n) Considerations:

<Describe any issues related to internationalization; if there are none, say "none" and justify>

Requirements:

Protocol Requirements

<Write the protocols that are required or usually used in your use case. Write "flexible" if it does not matter.>

Content Type Requirements

<Write the content types that are required or usually used in your use case. Write "flexible" if it does not matter,>

Platform or Standard Requirements

<Write the platforms or standards that are required or usually used in your use case. Write "none" if there is none.>

Authentication and Authorization Mechanisms Requirements

<Write the authentication and authorization mechanisms that are required or usually used in your use case. Write "flexible" if it does not matter, "none" if your use case requires that there is no authentication.>

Gaps:

Existing standards:

Comments: