{"id":347136,"date":"2024-10-20T00:24:43","date_gmt":"2024-10-20T00:24:43","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-iso-iec-29341-28-12017\/"},"modified":"2024-10-25T23:54:01","modified_gmt":"2024-10-25T23:54:01","slug":"bs-iso-iec-29341-28-12017","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-iso-iec-29341-28-12017\/","title":{"rendered":"BS ISO\/IEC 29341-28-1:2017"},"content":{"rendered":"
Today multi-screen\/second-screen solutions are proliferating. However, each is a proprietary vertical for particular vendor(s). Therefore users expectations aren\u2019t being met:<\/p>\n
Seamless interoperability across vendors.<\/p>\n<\/li>\n
Ability for second screen integrated usages rather than 100s of different apps.<\/p>\n<\/li>\n<\/ul>\n
The UPnP Multi-Screen Device Control Protocols (DCPs) provide an open interface to enable this interoperability between devices and applications, i.e. enable time-sensitive and interactive services, including implementation-specific applications, among various display devices.<\/p>\n
This document describes the overall Multi-Screen Architecture, which forms the foundation for the UPnP Multi-Screen Device and Service templates. The Multi-Screen Architecture defines the general interaction between UPnP control points and UPnP devices defined by the UPnP Multi-Screen DCPs.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | National foreword <\/td>\n<\/tr>\n | ||||||
6<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 3 Terms, definitions, symbols and abbreviations <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 4 Notations and Conventions 4.1 Notation 4.1.1 Data Types <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 4.1.2 Strings Embedded in Other Strings 4.2 Derived Data Types 4.2.1 CSV Lists <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 4.2.2 XML Document <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 4.2.3 XML Fragment 4.3 Management of XML Namespaces in Standardized DCPs <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 4.3.1 Namespace Prefix Requirements <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 4.3.2 Namespace Names, Namespace Versioning and Schema Versioning <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 4.3.3 Namespace Usage Examples 4.4 Vendor-defined Extensions 4.4.1 Vendor-defined Action Names <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 4.4.2 Vendor-defined State Variable Names 4.4.3 Vendor-defined XML Elements and attributes 5 Multi-Screen Architectural Overview 5.1 Screen Device <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 5.2 Screen Control Point <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Information technology. UPnP Device Architecture – Multiscreen device control protocol. Multiscreen architecture<\/b><\/p>\n |