Proposal to start work on Architecture and Requirements for Web-based Signage Player - Emergency Information Profile

Dear All,

Hello, everyone. It’s been a while.
I see that Futomi has worked on core profile, and no progress on other profiles.
We also have been busy with other business matter, so we could not make comments or contributions to the work that is going on in this BG.
There has not been much activity in here for few months. So I think we need to start on something in order to make progress.

We have been sort of interested in emergency information, so we would like to make proposal on starting the work on the “Architecture and Requirements for Web-based Signage Player - Emergency Information Profile”.
We believe that Emergency Information should be handled in somewhat unified manner (display format) for the people to easily perceive and understand the information to minimize confusion during emergency.
Actual style and format of expressing the emergency information are national regulatory matter; however, web-based signage BG can suggest a profile for emergency information service using web technology.
So, from this assumption, I think we can work on “Architecture and Requirements for Web-based Signage Player - Emergency Information Profile”.

Some of the work list we think that can be considered is as follows
-          Overview of emergency information system for digital signage: this part provides brief description of the overall lifecycle of emergency information that can be displayed in the digital signage system. Normally emergency information is officially generated by the national disaster related center such as weather center or national relief organization. This part can describe the overall structure of emergency information system and describes how the information data may be processed by the digital signage system in general.
-          Classification of Severity Level for display: the emergency information should be displayed differently according to the seriousness and urgency. Same information can have different impact according to the circumstances. For example, emergency information such as weather, emergency status of other area is informational and can be classified as minor alarm. Information such as earthquake, tsunami, and fire that involve threats to the surrounding are classified as major alarm. This part assumes there are different levels of alerts/alarm which can vary from minor alarm (such as weather, emergency news of other area) to major alarm (such as earthquake, tsunami, fire, etc.) that involves threats to the surrounding. This part intends to classify the severity levels and suggests method of display that can be used for each level. Some display method can include such as display format, display frequency, type of sound produced, etc. We can draw some requirements for each level in this process and make some gap analysis that may be needed. This part classifies the Severity Level based on the seriousness and urgency of the emergency information. It will not classify the actual type of emergency, since this is a national regulatory matter and is out of scope of W3C. For example, it will not assign earthquake as level something.
-          Reception of emergency information: this part can describe how the emergency information can be received by the digital signage system using web technology. We are considering WebSocket or HTTP PUSH for this.
-          Display of emergency information: this part describes how to display the emergency information using web technology. There can be various methods to consider in displaying emergency message, from use of ticker box, small window pop-up, full screen display with warning alarm, etc. This part can list some of the related web-technology that maybe used and include some example codes.
I believe we can work on the topics described above. I believe the work should be aligned with the core profile. For example, terminology, structure of the document, etc. There can be other topics that can be considered in this work. Any comments or ideas are welcome.

I think we need a space to work on this proposal and also to collect comments and ideas. We will try to make a skeleton for this work in the W3C wiki, maybe by next week, if there is no objection.

Regards,
Wook & Sung Hei