Siemens HiPath optiPoint 410 Developer's Manual
  1. Manuals
  2. Brands
  3. Siemens Manuals
  4. Control Unit
  5. HiPath optiPoint 410
  6. Developer's manual
Siemens HiPath optiPoint 410 Developer's Manual

Siemens HiPath optiPoint 410 Developer's Manual

Xml applications
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
HiPath
optiPoint application module
XML Applications
Developer's Guide

Advertisement

Table of Contents
loading

Related Manuals for Siemens HiPath optiPoint 410

Summary of Contents for Siemens HiPath optiPoint 410

  • Page 1 HiPath optiPoint application module XML Applications Developer’s Guide...

  • Page 2: Table Of Contents

    bkIVZ.fm For internal distribution only 1 Introduction ............2 1.1 Overview .

  • Page 3: Introduction

    XML documents using an XML schema is recommended (see Section 6.2, "XML Schema"). This document is meant for use by Siemens internal developers as well as by third party appli- cation developers. It contains the following sections: •...

  • Page 4: Prerequisites

    c01.fm Introduction Prerequisites • XML Object Reference • Push Technology • Appendix Prerequisites The following components and tools are required for developing applications for the application platform: optiPoint phone, type optiPoint 410 standard/advance or optiPoint 420 standard/advance A DSM (display module) or APM (application module) must be connected to the telephone. Infrastructure: •...

  • Page 5: Functions And Features

    c01.fm Functions and Features Infrastructure Functions and Features Infrastructure The following diagram shows the lines of communication between the various components: optiPoint optiPoint optiPoint optiPoint application module Application Server / Web Server 18. May 2006 optiPoint application module - XML Applications, Developer’s Guide...

  • Page 6: Basic Functionality

    c01.fm Functions and Features Basic Functionality Basic Functionality The following diagram shows the basic functions of the application: IP Phone 410/420 Server DSM or APM Java Business Environment Logic Display Application Keypad HTTP/HTTPS Webserver Parser The functional process of an application can be described as follows: The user installs an application on the optiPoint phone.

  • Page 7: Push Technology

    c01.fm Functions and Features Push Technology Push Technology Push technology makes it possible for the program to be started and, therefore, the data to be pushed from the server-side. With Push technology, a program on the server calls a specified URL for the IP phone and prompts it to load a specific XML document from a specific server.

  • Page 8: Installation And Starting The Program

    c01.fm Installation and Starting the Program Generating a Program on the Telephone Installation and Starting the Program Generating a Program on the Telephone Programs for the application platform described here are generated using the Web Based Man- ager. For this, the following steps are necessary: Enter the IP address of the telephone in the web browser.
  • Page 9 c01.fm Installation and Starting the Program Generating a Program on the Telephone • It cannot be longer than 20 characters. • Server Address: The IP address or domain/host name of the server (example, www.domain.de) that provides the application or the XML document. •...

  • Page 10: Starting The Program

    c01.fm Installation and Starting the Program Starting the Program select the program that you would like to configure or delete from the Program List pull- down menu. If you would like to reconfigure the program, change the respective parameters. For more information about these parameters, see Section 3, "Installation and Starting the Program".

  • Page 11: Xml Object Reference

    The names of the basic XML elements are prefixed with "Ipp" which stands for "IP phone", for example, "IppAction". Examples of the individual objects are provided. You will find the associated XML > files under: http://siemens.com/hipath The following table gives an overview of the individual objects and their function: Category Object Functional Description...

  • Page 12: Phone

    c01.fm XML Object Reference Phone Category Object Functional Description Hidden data Hidden Invisible field for transmitting data between telephone transfer and server Visualization Form/Gauge (not in- Horizontal bar that grows with adjustable speed of chronologi- teractive) cal processes Sending data Command (SE- The data contained in the entry fields on the screen are to the server...

  • Page 13: Display

    c01.fm XML Object Reference Display Display This object enables multiple screens within a single XML document. A screen corresponds to the content that is simultaneously shown on the display, comparable to a web page. According- ly, the IppScreen element functions as the root element of an XML document and, therefore, as the container for various screen objects, comparable to cards in an WML document.
  • Page 14 c01.fm XML Object Reference Screen Number of All Command objects are displayed. IppCommand (mandatory) Command ob- jects All Command elements are ignored. A number All the Command elements that exceed the number in- greater than dicated are ignored. the actual number of Command ob- jects...

  • Page 15: Action

    A call made to the telephone number specified in the TYPE (mandatory) child element <Number> is pushed. The action type "MAKECALL" can be executed on the models Siemens > optiPoint 410/420 410/420 standard and advance in the SIP and in the HFA variants. Syntax <IppAction Type="MAKECALL">...

  • Page 16: Command

    c01.fm XML Object Reference Command Command This object generates a softkey on the lower edge of the display, comparable to the do element in WML. A maximum of two softkeys can be displayed simultaneously on a screen. If there are more than two Command elements, the second softkey is labeled as "Menu"...
  • Page 17 c01.fm XML Object Reference Command Syntax <IppCommand Type="SELECT|BACK|UPDATE|SCREEN" Priority="[Number]" Au- to="[Number]" Key="[Key]" Value="[Value]"> <Label> </Label> <ScreenID> </ScreenID> </IppCommand> Multiple occurrences of a type can appear on a screen as long as each occurrence > is uniquely distinguishable. If two or more occurrences are not distinguishable from each other, the second as well as any further occurrences are ignored.

  • Page 18: Alert

    c01.fm XML Object Reference Alert Screenshot Alert An Alert is a message window that temporarily replaces the currently displayed screen. Differ- ent types of Alert can be selected using the Type attribute. Title, text as well as an image can be specified in the child elements.
  • Page 19 c01.fm XML Object Reference Alert Syntax <IppAlert Type="ALARM|CONFIRMATION|INFO|WARNING" Delay="[Number]|FOR- EVER"> <Title> </Title> <Text> </Text> <Image Cache="n"> </Image> </IppAlert> Child elements • Title The title of the Alert is displayed in the title bar. • Text Text in an Alert. • Image The image for the Alert.
  • Page 20 c01.fm XML Object Reference Alert Example <?xml version="1.0" encoding="UTF-8" ?> <IppDisplay> <IppScreen ID="1" HiddenCount="0" CommandCount="1"> <IppForm ItemCount="1"> <Title>Test Confirmation Alert</Title> <Url>http://subdomain.domain/path/program</Url> <IppStringItem> <Label>Press Alert</Label> <Text>for Confirmation Alert</Text> </IppStringItem> </IppForm> <IppCommand Type="SCREEN" Priority="0"> <Label>Alert</Label> <ScreenID>2</ScreenID> </IppCommand> </IppScreen> <IppScreen ID="2" HiddenCount="0" CommandCount="0"> <IppAlert Type="CONFIRMATION"...

  • Page 21: List

    c01.fm XML Object Reference List List This object represents a selection list comparable to the <select> and <option> elements in HTML or WML. A screen can only contain one List object. There are three types of selection lists: "IMPLICIT", "EXCLUSIVE" and "MULTIPLE". While the types "IMPLICIT"...
  • Page 22 c01.fm XML Object Reference List Syntax <IppList Type="IMPLICIT|EXCLUSIVE|MULTIPLE" Count="[Number]"> <Title> </Title> <Url> </Url> <Option ID="[Number]" Selected="FALSE|TRUE" Key="[Key]" Val- ue="[Value]"> <OptionText> </OptionText> <Image Cache="[Name]"> </Image> </Option> </IppList> Child elements • Title Title text for the selection list. The title is displayed in the system bar. •...
  • Page 23 c01.fm XML Object Reference List If a key or value is missing or the values are invalid, the key/value pair ’0-0’ is > sent. • OptionText Descriptive text for the option. • Image Illustrative image for the option. The image is displayed to the left of the text. For more in- formation about the Image element, see Section 4.12, "Image".
  • Page 24 c01.fm XML Object Reference List Screenshot 18. May 2006 optiPoint application module - XML Applications, Developer’s Guide...

  • Page 25: Textbox

    c01.fm XML Object Reference TextBox TextBox The user can enter text in a textbox. Predefined content, a title for the textbox, the permitted data types (Constraint) as well as a URL can be specified for sending the data to a server. The following attributes are available to the IppTextBox element: Attribute Value...
  • Page 26 c01.fm XML Object Reference TextBox Syntax <IppTextBox MaxSize="[Number]" Constraint="ANY|NUMERIC|PASS- WORD|PHONENUMBER|URL|EMAILADDR" Default="NULL|TEXT|PHONENUMBER" Key="[Key]"> <Title> </Title> <Text> </Text> <Url> </Url> </IppTextBox> Child elements • Title Title of the textbox. This is displayed in the system bar. • Text Predefined text contained in the textbox. •...
  • Page 27 c01.fm XML Object Reference TextBox Screenshot 18. May 2006 optiPoint application module - XML Applications, Developer’s Guide...

  • Page 28: Ticker

    c01.fm XML Object Reference Ticker Ticker Ticker text is displayed in the system bar and continually moves from right to left above the dis- play. Syntax <IppTicker> <Text> </Text> </IppTicker> If the text is missing or is invalid, an empty ticker, unnoticeable to the user, is dis- >...

  • Page 29: Hidden

    c01.fm XML Object Reference Hidden Screenshot 4.10 Hidden The function of this object is comparable to that of hidden entry fields in HTML. This makes it possible to not only receive data from the server using key/value pairs but to also send data to the server without these data being visible to the user.
  • Page 30 c01.fm XML Object Reference Hidden Syntax <IppHidden Type="VALUE|PHONENUMBER|IPADDRESS" Key="[Key]"> <Value> </Value> </IppHidden> Child elements • Value This contains the value that is sent to the server. Together with the Key attribute of the Ip- pHidden element, the content of Value builds a key/value pair. Example <?xml version="1.0"...

  • Page 31: Form

    c01.fm XML Object Reference Form 4.11 Form The Form object is used to generate a frame that provides certain layout options for a screen. With regard to the structure of XML, the IppForm element represents a container for the ele- ments StringItem, ImageItem, Spacer, TextField, DateField, ChoiceGroup and Gauge.
  • Page 32 c01.fm XML Object Reference Form 4.11.1 Form/StringItem This object provides a read-only text field. The text field consists of a label and the actual text. The text follows the label on the same line, separated by a simple space. The characters ’&’, ’<’, ’>’, ’"’ and ’’’ must be represented by the corresponding char- >...
  • Page 33 c01.fm XML Object Reference Form Example <?xml version="1.0" encoding="UTF-8" ?> <IppDisplay> <IppScreen ID="1" HiddenCount="0" CommandCount="1"> <IppForm ItemCount="1"> <Title>Form String</Title> <Url>http://subdomain.domain/path/program</Url> <IppStringItem> <Label>String1Label</Label> <Text>String1Text</Text> </IppStringItem> </IppForm> <IppCommand Type="SELECT" Priority="0"> <Label>Select</Label> <ScreenID>1</ScreenID> </IppCommand> </IppScreen> </IppDisplay> Screenshot 18. May 2006 optiPoint application module - XML Applications, Developer’s Guide...
  • Page 34 c01.fm XML Object Reference Form 4.11.2 Form/ImageItem This object functions as a frame for linking an image in the screen layout within a Form object.It enables control over the positioning of the image and the data for alternative text if the image cannot be displayed, as well as the addition of a label.
  • Page 35 c01.fm XML Object Reference Form Example <?xml version="1.0" encoding="UTF-8" ?> <IppDisplay> <IppScreen ID="1" HiddenCount="0" CommandCount="1"> <IppForm ItemCount="1"> <Title>Sunset</Title> <Url>http://subdomain.domain/path/program</Url> <IppImageItem Layout="CENTER"> <Label> </Label> <Image>http://subdomain.domain/path/image.png</Image> <AltText>Image1</AltText></IppImageItem> </IppForm> <IppCommand Type="SELECT" Priority="0"> <Label>Select</Label> <ScreenID>1</ScreenID> </IppCommand> </IppScreen> </IppDisplay> Screenshot 18. May 2006 optiPoint application module - XML Applications, Developer’s Guide...
  • Page 36 c01.fm XML Object Reference Form 4.11.3 Form/Spacer The Spacer object is used to structure the layout within a Form object. It generates a line break at a specified position. Without the Spacer object, all the subelements in a form are displayed inline, that is, without line breaks.
  • Page 37 c01.fm XML Object Reference Form Example <?xml version="1.0" encoding="UTF-8" ?> <IppDisplay> <IppScreen ID="1" HiddenCount="0" CommandCount="1"> <IppForm ItemCount="3"> <Title>Test Newline Begin</Title> <Url>http://subdomain.domain/path/program</Url> <IppTextField MaxSize="30" Constraint="ANY" Default="TEXT" Key="TF2"> <Label>First Text</Label> <Text>abc123</Text> </IppTextField> <IppSpacer NewLine="BEGIN" /> <IppTextField MaxSize="30" Constraint="ANY" Default="TEXT" Key="TF2"> <Label>Second Text</Label> <Text>xyz890</Text>...
  • Page 38 c01.fm XML Object Reference Form 4.11.4 Form/TextField An entry field for data is generated, comparable to the input tag in HTML. The entry field con- tains a label. In addition, the data type of the entry can be defined using the Constraint attribute. The following attributes are available to the TextField element: Attribute Value...
  • Page 39 c01.fm XML Object Reference Form Syntax <IppTextField MaxSize="[Number]" Constraint="ANY|NUMERIC|PASS- WORD|PHONENUMBER|URL|EMAILADDR" Default="NULL|TEXT|PHONENUMBER" Key="[Key]"> <Label > </Label > <Text> </Text> </IppTextField > Child elements • Label Label for identifying the entry field. The label is displayed above the entry field. • Text Text that is preset in the entry field.
  • Page 40 c01.fm XML Object Reference Form Example <?xml version="1.0" encoding="UTF-8" ?> <IppDisplay> <IppScreen ID="1" HiddenCount="0" CommandCount="1"> <IppForm ItemCount="3"> <Title>Form String</Title> <Url>http://subdomain.domain/path/program</Url> <IppTextField MaxSize="30" Constraint="NUMERIC" De- fault="TEXT" Key="TF1"> <Label>Numeric Text</Label> <Text>123456</Text> </IppTextField> <IppTextField MaxSize="30" Constraint="ANY" Default="TEXT" Key="TF2"> <Label>Any Text</Label> <Text>abc123</Text> </IppTextField> <IppTextField MaxSize="30" Constraint="PASSWORD" De- fault="TEXT"...
  • Page 41 c01.fm XML Object Reference Form Screenshot 4.11.5 Form/ChoiceGroup This element, together with its child elements, forms a selection list within a form, comparable to the <select> and <option> elements in HTML and WML. There are two types of ChoiceGroups: "EXCLUSIVE" and "MULTIPLE". While only one single option is permitted for the type "EXCLUSIVE", the type "MULTIPLE"...
  • Page 42 c01.fm XML Object Reference Form Number of op- Only as many options as indicated here are displayed. Count (mandatory) tions If the actual number of options is greater, all further op- tions that exceed this setting are ignored. No options are displayed. Syntax <IppChoiceGroup Type="EXCLUSIVE|MULTIPLE"...
  • Page 43 c01.fm XML Object Reference Form Descriptive text for the option. • Image Illustrative image for the option. The image is displayed to the left of the text. For more in- formation about the Image element, see Section 4.12, "Image". Example <?xml version="1.0"...
  • Page 44 c01.fm XML Object Reference Form </IppCommand> </IppScreen> </IppDisplay> Screenshot 18. May 2006 optiPoint application module - XML Applications, Developer’s Guide...
  • Page 45 c01.fm XML Object Reference Form 4.11.6 Form/DateField The object generates a field, in which date and time information can be prespecified or entered by the user. The DateField contains a label. The data to be displayed (date, time, date and time) as well as the time zone can be specified.
  • Page 46 c01.fm XML Object Reference Form Child elements • Label Generates a label for identifying the respective fields. The label is displayed above the fields. • TimeZone Entry for the time zone. • Date Entry for the date in the order of day - month - year. The YYYY-MM-DD format is used for indicating the date in the XML document, >...
  • Page 47 c01.fm XML Object Reference Form Example <?xml version="1.0" encoding="UTF-8" ?> <IppDisplay> <IppScreen ID="1" HiddenCount="0" CommandCount="1"> <IppForm ItemCount="3"> <Title>Form Date</Title> <Url>http://subdomain.domain/path/program</Url> <IppDateField Mode="TIME" Default="MODE" DateKey="DK1" TimeKey="TK1"> <Label>Time</Label> <TimeZone>GMT+1</TimeZone> <Date>2005-04-08</Date> <Time>13:00:00.000</Time> </IppDateField> <IppDateField Mode="DATE" Default="MODE" DateKey="DK2" TimeKey="TK2"> <Label>Date</Label> <TimeZone>GMT + 1</TimeZone> <Date>2005-04-09</Date> <Time>13:00:00.000</Time>...
  • Page 48 c01.fm XML Object Reference Form Screenshot 4.11.7 Form/Button The Button object generates a clickable area. When clicked, the key/value pair contained in the attributes of the IppButton element as well as the key/value pairs the Hidden objects in the XML document (see Section 4.10, "Hidden") are sent to the server, the URL of which is indicat- ed in the Form element.
  • Page 49 c01.fm XML Object Reference Form Attribute Value Function Value The value of the key/value pair that is sent to the Value (mandatory) server. Table 4-5 Syntax <IppButton Type="IMAGE" Layout="[CENTER|DE- FAULT|LEFT|NEWLINE_AFTER|NEWLINE_BEFORE|RIGHT]" Key="[Key]" Val- ue="[Value]"> <Label> </Label> <Image Cache="n"> </Image> </IppButton> Child elements •...
  • Page 50 c01.fm XML Object Reference Form Example <?xml version="1.0" encoding="UTF-8" ?> <IppDisplay> <IppScreen ID="1" HiddenCount="0" CommandCount="1"> <IppForm ItemCount="1"> <Title>Form String</Title> <Url>http://subdomain.domain/path/program</Url> <IppButton Type="IMAGE" Layout="CENTER" Key="KEY" Val- ue="WERT"> <Label>Hit this button: </Label> <Image>inCall.png</Image> </IppButton> </IppForm> <IppCommand Type="SELECT" Priority="0"> <Label>Select</Label> <ScreenID>1</ScreenID> </IppCommand> </IppScreen> </IppDisplay>...
  • Page 51 c01.fm XML Object Reference Form 4.11.8 Form/Gauge A value is represented graphically using a horizontal status bar. A label is provided to identify the value. Depending on what is specified, the value can be set by the user and sent to a server (slider functionality) or be made dependent on processes which last a longer period of time (e.
  • Page 52 c01.fm XML Object Reference Form USER: The number entered here in the range 0-100 indicates the maximum value that can be sent to the server. If the maximum value is set at under 100, for instance, at 80, the status bar will >...

  • Page 53: Image

    c01.fm XML Object Reference Image Screenshot 4.12 Image The Image element is used to link an image. It can be specified whether the image should be cached or not. The image can be linked in two ways: 1) a file on the server is downloaded per HTTP or 2) a predefined image file in the telephone software is used (for more information, see Section 2.4, "Using Predefined Images").
  • Page 54 c01.fm XML Object Reference Image Syntax <Image Cache="[Name]"> </Image> The content of the Image element indicates the source of the image to be displayed. Depending on the situation, this value may have various formats: A predefined image that is already available in the telephone software: •...

  • Page 55: Push Technology

    c01.fm Push Technology Image Push Technology A Push request to an optiPoint phone is a specific HTTP POST request that is sent to the Web service of the telephone. The Push request is sent to the following URL: http://<phone IP address>:<phone port>/server_push.html/ServerPush Example: http://137.223.234.11:8085/server_push.html/ServerPush The Push request must contain the following Information:...
  • Page 56 c01.fm Push Technology Image The following table gives information about the behavior of the IP phone in various conditions for various types of Push requests: Application status Push request type and phone behavior queue indicate force Installed, not run- Starts the application, loads the XML document from the server and ning shows it on the display.

  • Page 57: Appendix

    The XML schema printed here may deviate from the current version. You can down- > load the current version here: http://www.siemens.com/hipath <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:annotation> <xs:documentation xml:lang="en"> XML Schema for Siemens IP Phone Generic MIDlet. Copyright 2005 Siemens plc. All rights reserved. </xs:documentation> </xs:annotation> <xs:element name="IppPhone"> <xs:complexType> <xs:sequence> 18. May 2006...
  • Page 58 c01.fm Appendix XML Schema <xs:choice> <xs:element ref="IppDisplay"/> </xs:choice> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="IppDisplay"> <xs:complexType> <xs:sequence> <xs:element ref="IppScreen" minOccurs="1" maxOccurs="20"/ > </xs:sequence> <xs:attribute name="InitialScreen" type="xs:nonNegativeInte- ger"/> </xs:complexType> </xs:element> <xs:element name="IppScreen"> <xs:complexType> <xs:sequence> <xs:choice> <xs:element ref="IppAlert"/> <xs:element ref="IppList"/> <xs:element ref="IppTextBox"/> <xs:element ref="IppTicker"/> <xs:element ref="IppForm"/>...
  • Page 59 c01.fm Appendix XML Schema <xs:element ref="IppCommand" minOccurs="0" maxOccurs="un- bounded"/> <xs:element ref="IppHidden" minOccurs="0" maxOccurs="un- bounded"/> <xs:element ref="IppTicker" minOccurs="0" maxOccurs="1"/> </xs:sequence> <xs:attribute name="HiddenCount" default="0" type="xs:nonNe- gativeInteger"/> <xs:attribute name="CommandCount" default="0" type="xs:non- NegativeInteger"/> <xs:attribute name="ID" default="0" type="xs:nonNegativeIn- teger"/> </xs:complexType> </xs:element> <xs:element name="IppAction"> <xs:complexType> <xs:sequence> <xs:element name="Number"...
  • Page 60 c01.fm Appendix XML Schema <xs:enumeration value="ENDCALL" /> </xs:restriction> </xs:simpleType> </xs:attribute> </xs:complexType> </xs:element> <xs:element name="IppAlert"> <xs:complexType> <xs:sequence> <xs:element ref="Title" minOccurs="0" maxOccurs="1"/> <xs:element ref="Text" minOccurs="0" maxOccurs="1"/> <xs:element ref="Image" minOccurs="0" maxOccurs="1"/> </xs:sequence> <xs:attribute name="Type" default="ERROR"> <xs:simpleType> <xs:restriction base="xs:string" > <xs:enumeration value="ALARM" /> <xs:enumeration value="CONFIRMATION" /> <xs:enumeration value="ERROR"...
  • Page 61 c01.fm Appendix XML Schema <xs:simpleType> <xs:restriction base="xs:positiveInteger"/> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="FOREVER"/> </xs:restriction> </xs:simpleType> </xs:union> </xs:simpleType> </xs:attribute> </xs:complexType> </xs:element> <xs:element name="IppChoiceGroup"> <xs:complexType> <xs:sequence> <xs:element ref="Label" minOccurs="0" maxOccurs="1"/> <xs:element ref="Option" minOccurs="0" maxOccurs="un- bounded"/> </xs:sequence> <xs:attribute name="Numbered" default="NO"> <xs:simpleType> <xs:restriction base="xs:string" > <xs:enumeration value="NO"...
  • Page 62 c01.fm Appendix XML Schema <xs:attribute name="Type" default="EXCLUSIVE"> <xs:simpleType> <xs:restriction base="xs:string" > <xs:enumeration value="EXCLUSIVE" /> <xs:enumeration value="MULTIPLE" /> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:attribute name="Count" default="0" type="xs:nonNega- tiveInteger"/> </xs:complexType> </xs:element> <xs:element name="IppCommand"> <xs:complexType> <xs:sequence> <xs:element name="Label" minOccurs="1" maxOccurs="1" type="xs:string"/> <xs:element name="ScreenID" minOccurs="0" maxOccurs="1" type="xs:nonNegativeInteger"/>...
  • Page 63 c01.fm Appendix XML Schema <xs:enumeration value="EXIT" /> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:attribute name="Priority" default="0"> <xs:simpleType> <xs:restriction base="xs:nonNegativeInteger"> <xs:maxInclusive value="9"/> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:attribute name="Auto" default="0"> <xs:simpleType> <xs:restriction base="xs:nonNegativeInteger"/> </xs:simpleType> <xs:attribute name="Auto" default="0"/> <xs:attribute ref="Key"/> <xs:attribute ref="Value"/> </xs:complexType> </xs:element> <xs:element name="IppDateField"> <xs:complexType> <xs:sequence>...
  • Page 64 c01.fm Appendix XML Schema </xs:sequence> <xs:attribute name="Mode" default="DATETIME"> <xs:simpleType> <xs:restriction base="xs:string" > <xs:enumeration value="DATE" /> <xs:enumeration value="TIME" /> <xs:enumeration value="DATETIME" /> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:attribute name="Default" default="NULL"> <xs:simpleType> <xs:restriction base="xs:string" > <xs:enumeration value="NULL" /> <xs:enumeration value="MODE" /> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:attribute ref="DateKey"...
  • Page 65 c01.fm Appendix XML Schema <xs:element ref="IppChoiceGroup" minOccurs="0" maxOc- curs="unbounded"/> <xs:element ref="IppDateField" minOccurs="0" maxOc- curs="unbounded"/> <xs:element ref="IppGauge" minOccurs="0" maxOccurs="un- bounded"/> <xs:element ref="IppImageItem" minOccurs="0" maxOc- curs="unbounded"/> <xs:element ref="IppSpacer" minOccurs="0" maxOccurs="un- bounded"/> <xs:element ref="IppStringItem" minOccurs="0" maxOc- curs="unbounded"/> <xs:element ref="IppTextField" minOccurs="0" maxOc- curs="unbounded"/> </xs:sequence> <xs:attribute name="ItemCount"...
  • Page 66 c01.fm Appendix XML Schema <xs:enumeration value="AUTO" /> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:attribute ref="Key" use="required"/> </xs:complexType> </xs:element> <xs:element name="IppHidden"> <xs:complexType> <xs:sequence> <xs:element ref="Value" minOccurs="0" maxOccurs="1"/> </xs:sequence> <xs:attribute name="Type" default="VALUE"> <xs:simpleType> <xs:restriction base="xs:string" > <xs:enumeration value="VALUE" /> <xs:enumeration value="PHONENUMBER" /> <xs:enumeration value="IPADDRESS" /> </xs:restriction>...
  • Page 67 c01.fm Appendix XML Schema <xs:sequence> <xs:element ref="Label" minOccurs="0" maxOccurs="1"/> <xs:element ref="Image" minOccurs="0" maxOccurs="1"/> <xs:element ref="AltText" minOccurs="0" maxOccurs="1"/> </xs:sequence> <xs:attribute name="Layout" default="CENTER"> <xs:simpleType> <xs:restriction base="xs:string" > <xs:enumeration value="CENTER" /> <xs:enumeration value="DEFAULT" /> <xs:enumeration value="LEFT" /> <xs:enumeration value="NEWLINE_AFTER" /> <xs:enumeration value="NEWLINE_BEFORE" /> <xs:enumeration value="RIGHT"...
  • Page 68 c01.fm Appendix XML Schema <xs:simpleType> <xs:restriction base="xs:string" > <xs:enumeration value="NO" /> <xs:enumeration value="YES" /> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:attribute name="Type" default="IMPLICIT"> <xs:simpleType> <xs:restriction base="xs:string" > <xs:enumeration value="IMPLICIT" /> <xs:enumeration value="EXCLUSIVE" /> <xs:enumeration value="MULTIPLE" /> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:attribute name="Count" default="0" type="xs:nonNega- tiveInteger"/>...
  • Page 69 c01.fm Appendix XML Schema <xs:restriction base="xs:string" > <xs:enumeration value="BEGIN" /> <xs:enumeration value="BOTH" /> <xs:enumeration value="END" /> </xs:restriction> </xs:simpleType> </xs:attribute> </xs:complexType> </xs:element> <xs:element name="IppStringItem"> <xs:complexType> <xs:sequence> <xs:element ref="Label" minOccurs="0" maxOccurs="1"/> <xs:element ref="Text" minOccurs="0" maxOccurs="1"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="IppTextBox"> <xs:complexType> <xs:sequence> <xs:element ref="Title"...
  • Page 70 c01.fm Appendix XML Schema <xs:simpleType> <xs:restriction base="xs:string" > <xs:enumeration value="ANY" /> <xs:enumeration value="NUMERIC" /> <xs:enumeration value="PASSWORD" /> <xs:enumeration value="PHONENUMBER" /> <xs:enumeration value="URL" /> <xs:enumeration value="EMAILADDR" /> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:attribute ref="DefaultText" use="required"/> <xs:attribute ref="Key" use="required"/> </xs:complexType> </xs:element> <xs:element name="IppTextField"> <xs:complexType> <xs:sequence>...
  • Page 71 c01.fm Appendix XML Schema <xs:enumeration value="PASSWORD" /> <xs:enumeration value="PHONENUMBER" /> <xs:enumeration value="URL" /> <xs:enumeration value="EMAILADDR" /> <xs:enumeration value="VALIDATE" /> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:attribute ref="DefaultText" use="required"/> <xs:attribute ref="Key" use="required"/> </xs:complexType> </xs:element> <xs:element name="IppTicker"> <xs:complexType> <xs:sequence> <xs:element ref="Text" minOccurs="0" maxOccurs="1"/> </xs:sequence> </xs:complexType> </xs:element>...
  • Page 72 c01.fm Appendix XML Schema <xs:union> <xs:simpleType> <xs:restriction base="xs:string"/> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"/> <xs:pattern value="/.+"/> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"/> <xs:pattern value="http.+"/> </xs:simpleType> </xs:union> </xs:sequence> <xs:attribute name="Cache" type="xs:string"/> </xs:complexType> </xs:element> <xs:element name="Initial" type="gaugeTimeType"/> <xs:element name="Label" type="xs:string"/> <xs:element name="Maximum" type="gaugeTimeType"/> <xs:element name="OptionText" type="xs:string"/> <xs:element name="Text"...
  • Page 73 c01.fm Appendix XML Schema <xs:element name="Timezone" type="timeZoneType"/> <xs:element name="Time" type="xs:time"/> <xs:element name="Title" type="xs:string"/> <xs:element name="Url" type="xs:anyURI"/> <xs:element name="Value" type="xs:string"/> <xs:element name="Option"> <xs:complexType> <xs:sequence> <xs:element ref="OptionText" minOccurs="1" maxOccurs="1"/ > <xs:element ref="Image" minOccurs="0" maxOccurs="1"/> </xs:sequence> <xs:attribute name="ID" type="xs:nonNegativeInteger"/> <xs:attribute name="Selected" default="FALSE"> <xs:simpleType> <xs:restriction base="xs:string"...
  • Page 74 c01.fm Appendix XML Schema <xs:attribute ref="TColor" /> <xs:attribute ref="SFColor"/> <xs:attribute ref="STColor"/> </xs:complexType> </xs:element> <xs:attribute name="DateKey" type="xs:string"/> <xs:attribute name="FColor" type="colourType"/> <xs:attribute name="Key" type="xs:string"/> <xs:attribute name="SFColor" type="colourType"/> <xs:attribute name="STColor" type="colourType"/> <xs:attribute name="TColor" type="colourType"/> <xs:attribute name="TimeKey" type="xs:string"/> <xs:attribute name="Value" type="xs:string"/> <xs:attribute name="DefaultText"> <xs:simpleType> <xs:restriction base="xs:string"...
  • Page 75 c01.fm Appendix XML Schema </xs:restriction> </xs:simpleType> </xs:attribute> <xs:simpleType name="gaugeTimeType"> <xs:union> <xs:simpleType> <xs:restriction base="xs:nonNegativeInteger"/> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:pattern value="\d{2}:\d{2}"/> </xs:restriction> </xs:simpleType> </xs:union> </xs:simpleType> <xs:simpleType name="timeZoneType"> <xs:union> <xs:simpleType> <xs:restriction base="xs:string"/> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string"> <xs:pattern value="GMT[+-]\d*"/> </xs:restriction> </xs:simpleType> </xs:union> 18. May 2006 optiPoint application module - XML Applications, Developer’s Guide...
  • Page 76 c01.fm Appendix XML Schema </xs:simpleType> <xs:simpleType name="colourType"> <xs:union> <xs:simpleType> <xs:restriction base="xs:string"> <xs:pattern value="#[0-9ABCDEF]{6}"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:string" > <xs:enumeration value="BLACK" /> <xs:enumeration value="RED" /> <xs:enumeration value="GREEN" /> <xs:enumeration value="BROWN" /> <xs:enumeration value="BLUE" /> <xs:enumeration value="MAGENTA" /> <xs:enumeration value="CYAN" /> <xs:enumeration value="LIGHTGRAY"...
  • Page 77 c01.fm Appendix XML Schema </xs:simpleType> </xs:union> </xs:simpleType> </xs:schema> 18. May 2006 optiPoint application module - XML Applications, Developer’s Guide...
  • Page 79 An obligation to provide the respective characteristics shall only exist if expressly agreed in the terms of contract. The trademarks used are owned by Siemens AG or their respective owners. © Siemens AG 2006 • Siemens Communications •...

This manual is also suitable for:

Hipath optipoint 420

Table of Contents