40 likes | 70 Views
Sub-setting Mechanisms. CAP is a technical Standard (specification) The CAP specification contains… Elements (settings, lists, extensions, etc..) Rules (multi-use vs. single, optional vs. required, etc…) A Profile is a sub-set of a standard A definition of use that may further define
E N D
Sub-setting Mechanisms • CAP is a technical Standard (specification) • The CAP specification contains… • Elements (settings, lists, extensions, etc..) • Rules (multi-use vs. single, optional vs. required, etc…) • A Profile is a sub-set of a standard • A definition of use that may further define • Elements and Rules
Sub-setting Mechanisms • An Alerting System is a business • Interoperable Alerting Systems need a business standard • A CAP based alerting Business Standard contains… • Managed Lists (events, geo-codes, etc..) • Layers (defined extensions) • Managed Prefixes (URN:OASIS:…, etc..) • A Profile is a sub-set of a standard • A definition of use that may further define • the Lists, Layers and Prefixes • not items specific to a system (such as “Broadcast Intrusive”)
Profiles • The CAP Canadian Profile includes… • a technical profile of CAP • a business profile of Public Alerting and CAP • Both profiles are needed for proper customization within… • a community of an Alerting System (i.e Canada’s NPAS) • the overall community of Alerting Systems (OASIS)
Questions? • Are there business profiles out there? • Is OASIS overseeing technical profiles? • Is there anything to oversee business profiles? • Is there List, Layer and Prefix management efforts? • Is there other aspects a business profile should involve? • This is tricky as this is CAP related as CAP is the common point of reference between Systems? • Tendency is to overdo the profile and bias CAP to any one system when building a system? • Bias has to be removed?