ISO IEC 23007-1 AMD 1-2012 Information technology - Rich media user interfaces - Part 1 Widgets - Amendment 1 Widget extensions《信息技术 多功能媒体用户界面 第1部分 窗体小部件 修改件1》.pdf

1、 Reference number ISO/IEC 23007-1:2010/Amd.1:2012(E) ISO/IEC 2012INTERNATIONAL STANDARD ISO/IEC 23007-1 First edition 2010-11-01 AMENDMENT 1 2012-01-15 Information technology Rich media user interfaces Part 1: Widgets AMENDMENT 1: Widget extensions Technologies de linformation Interfaces dutilisateu

2、r au support riche Partie 1: Widgets AMENDEMENT 1: Extensions de widget ISO/IEC 23007-1:2010/Amd.1:2012(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2012 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or m

3、echanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www

4、iso.org Published in Switzerland ii ISO/IEC 2012 All rights reservedISO/IEC 23007-1:2010/Amd.1:2012(E) ISO/IEC 2012 All rights reserved iiiForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldw

5、ide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in

6、fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are draft

7、ed in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an Intern

8、ational Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Am

9、endment 1 to ISO/IEC 23007-1:2010 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia information. This Amendment introduces extensions for advanced widgets and improves interoperability between widg

10、et managers. ISO/IEC 23007-1:2010/Amd.1:2012(E) ISO/IEC 2012 All rights reserved 1Information technology Rich media user interfaces Part 1: Widgets AMENDMENT 1: Widget extensions At the end of 6.1, add: In order to be discoverable by other widget managers and recognizable as an MPEG-U conformant imp

11、lementation, an MPEG-U widget manager shall advertise a service of type “urn:mpeg:mpeg- u:standard-service:widget-manager” on all the service and discovery protocols that it supports to manage the services offered or required by the widgets. Using this service, widget managers shall support the rece

12、ption of a “startWidget” message, with either a “widgetUrl” or a “widgetUUID” parameter, as strings, and optionally with a “widgetContext”, a string containing the widget context information as defined in Clause 11. The widget manager shall reply to this message with an integer parameter called “err

13、orCode”, whose value is 0 if the widget was successfully loaded and any other value if the loading failed. Using this service, widget managers shall support the reception of a “requestCapabilitiesList” message with no parameter. The widget manager shall reply with a message containing a description

14、of the processing capabilities of the widget manager. The description shall be formatted as a string in the “capabilities” parameter and may be empty. The format of this parameter may be given in the “capabilitiesType” in the form of a mime type. If this parameter is omitted, the default value is “a

15、pplication/xml”. Using this service, a widget manager can also query and request migration of widgets from another widget manager. The list of widgets can be retrieved using the listWidgets message, which allows a remote widget manager to query the list of possible widgets from the target widget man

16、ager. The reply contains a list of (numerical) codes, a list of widget names as a space-separated list of quoted strings, and an optional list of space-separated list of UUIDs. NOTE The selection of the widgets to be listed is implementation specific: a widget manager may decide to only list some ac

17、tivated widgets or all widgets installed, whether activated or not. A widget manager can then request the migration of a widget from the target widget manager using the getWidget message. This message instructs the target widget manager to trigger the migration of the widget whose code is provided.

18、The target widget manager then sends a startWidget message to the widget manager originating this message. The following error codes are defined: - errorCode 0: success - errorCode 1: requested widget is no longer available - errorCode 2: target widget manager denied sending of the widget - errorCod

19、e 3: any other error. NOTE The target widget manager may refuse to migrate a widget for security reasons. The mechanisms used by such a widget manager to certify other widget managers are outside the scope of this specification. NOTE The default value for capabilitiesType is application/xml as most

20、capability description standards use XML documents (e.g W3C CC/PP, MPEG-21 UED). ISO/IEC 23007-1:2010/Amd.1:2012(E) 2 ISO/IEC 2012 All rights reservedThe following code uses the syntax described in Clause 10 to describe this service. But, a widget shall not have this interface in its manifest and wi

21、dget managers shall fail to load any widget, which has such interface in its manifest. At end of 7.2 Widget life cycle, add: The widget manager shall maintain a set of known widgets: a known widget is a widget that the widget manager has checked that it can be rendered. One use of this set is to sea

22、rch for a component matching given interfaces, as described in 10.20. NOTE The widget manager may provide more services on known widgets, such as displaying a catalog of icons of known widgets. After the scriptParamType attribute description in 10.18, add: Possible values are boolean, number, string

23、 stringarray. The type stringarray is reserved for use within predefined communications with the widget manager. At the end of 10.19, add: mw:scriptParamType When used as a parameter within a mapping to a script function call, this attribute defines the type of the parameter on which this input is

24、mapped. Possible values are boolean, number, string, stringarray. The type stringarray is reserved for use within predefined communications with the widget manager. In 10.20 The element, replace the sentence: ISO/IEC 23007-1:2010/Amd.1:2012(E) ISO/IEC 2012 All rights reserved 3Upon loading of this m

25、anifest, the widget manager shall get the manifest of the component widgets referenced by the mw:src attribute or try to find a widget that matches the interfaces declared by the elements, without actually activating the component widget. with: Upon loading of this manifest, the Widget Manager shall

26、 get the manifest of the component widgets referenced by the mw:src attribute or try to find in its set of known widgets as defined in 7.2, a widget that matches the interfaces declared by the elements, without actually activating the component widget. At the end of 10.20, add: mw:activationTarget O

27、ptional. This attribute describes when and how the widget manager activating the component, called the local widget manager, may forward it, with the following possible values: localOnly (default): the local widget manager shall not forward this component to other widget managers. localAndAllRemote:

28、 the local widget manager shall activate this component and forward it to other remote widget managers. localOrSingleRemote: the local widget manager shall activate this component or, if local activation failed, shall forward it to a single remote widget manager. allRemote: the local widget manager

29、shall not activate this component and shall forward it to all the remote widget managers. singleRemote: the local widget manager shall not activate this component and shall forward it to a single remote widget manager. In the cases localOrSingleRemote and singleRemote, the widget manager shall try t

30、o load the component on all possible remote widget managers one by one and shall stop as soon as one load is successful. In the cases localAndAllRemote and allRemote, the widget manager shall try to load the component on all possible remote widget managers. At the end of 10.22, add: This message is

31、sent by a Widget to request that the Widget Manager adds the widget found at the given “url” parameter to its set of known widgets. The Widget Manager shall reply using a “returnCode” parameter whose value is: 1 for failure of the request and 0 for success. ISO/IEC 23007-1:2010/Amd.1:2012(E) 4 ISO/I

32、EC 2012 All rights reservedThis message is sent by a Widget to request that the Widget Manager activates the widget found at the given “url” parameter. The activated widget is not added to the set of known widgets. The Widget Manager shall reply using a “returnCode” parameter whose value is: 1 for f

33、ailure of the request and 0 for success. This message is sent by a Widget to request that the Widget Manager migrates the component widget with the id given by the “componentId” parameter. If the “targetCode” parameter is not supplied, the Widget Manager shall present the choice of migration targets

34、 to the user, by any appropriate means. If the “targetCode” parameter is supplied, the Widget Manager shall migrate the component widget to the designated target. The value of the target code shall be taken from a reply to the “requestMigrationTargets” message. The Widget Manager shall reply using a

35、 “returnCode” parameter whose value is: 1 for failure of the request and 0 for success. This message is sent by a Widget to request that the Widget Manager investigates what are the possible migration targets, i.e. devices a widget can be migrated to. The parameters “codes”, “names” and “description

36、s” shall be arrays of string values, with the same number of values in each of the three. The “codes” parameter shall contain the list of codes to be used for a migration target in the message “migrateComponent” above. The “names” parameter shall contain the list of names of migration targets. The “

37、descriptions” parameter shall contain the list of descriptions of migration targets. Add 10.24: 10.24 The element Description: This element identifies a set of alternative components. Upon activation of the componentChoice, the widget manager shall try, one by one, to load the component children, in

38、 document order. As soon as one component child activation succeeds, the widget manager stops. Context: This is a child of a element. Expected children (in any order): One or more elements, on which the attributes id, activateTrigger, deactivateTrigger, activatedAction, deactivatedAction, activateFa

39、ilureAction and activationTarget are not allowed. ISO/IEC 23007-1:2010/Amd.1:2012(E) ISO/IEC 2012 All rights reserved 5Attributes: mw:id Mandatory. Indicates an ID for the component group. The scope of this ID is limited to the widget. mw:activateTrigger Optional. Indicates the scene construct that

40、is used to trigger the activation of the component group. See 10.23.3 for the syntax. mw:deactivateTrigger Optional. Indicates the scene construct that is used to trigger the deactivation of the component widget. See 10.23.3 for the syntax. mw:activatedAction Optional. Indicates the name of a scene

41、construct that is used to receive the notification of the successful activation of the component widget. See 10.25 for the syntax. mw:deactivatedAction Optional. Indicates the name of a scene construct that is used to receive the notification of the deactivation of the component widget. See 10.25 fo

42、r the syntax. mw:activateFailureAction Optional. Indicates the scene construct that is used to receive the notification of the failure of the activation of the component widget. See10.23.2 for the syntax. mw:activationTarget Optional. Indicates when and how the widget manager activating the component may forward it. See10.20 for the syntax. ISO/IEC 23007-1:2010/Amd.1:2012(E) ICS 35.040 Price based on 5 pages ISO/IEC 2012 All rights reserved