Pre-configuring the URI List

The URI List framework provides support for pre-configuration of URIs in the list. This enables clients to pre-define URIs before shipping the device to end users. The URIs can be pre-configured to both BlackList and WhiteList. The pre-configuration also allows clients to secure such URIs by disabling removal or modification of the URIs.

The pre-configuration is done by creating an XML data file and installing it in a server's secure path. The pre-configuration happens only once, that is, when the first session with the server is created after installing the XML file. When the server is started and if the URI List is empty, the server checks for an XML file in its private path. If it exists, it copies the data to the list.

Note: You cannot pre-configure the list after you have added URIs to it.

Here are the steps to be performed for pre-configuration of the URI List:

Create the XML data file referring to the DTD shown in the URI List pre-configuration DTD section.
Create an SIS package containing this XML file. Sign it with ProtServ capability.

Note: The installation path of the XML file is c:\\private\\20009D70\\. The name of the XML file should be ineturilist.xml.
Install the SIS package.

URI List pre-configuration DTD

The DTD of URI List pre-configuration and a description of each element is given below.

<!--
Uri List pre-configuration Document Type Definition.

Copyright Symbian Software Pvt Ltd 2007. All rights reserved.  
-->

<?xml version="1.0" encoding="UTF-8" ?>
<!ELEMENT URIList (WAPPush, Browser, PushEMail, DevPro)> 
<!ELEMENT WAPPush (Whitelist, Blacklist)>
<!ELEMENT Browser (Whitelist, Blacklist)>
<!ELEMENT PushEMail (Whitelist, Blacklist)>
<!ELEMENT DevPro (Whitelist, Blacklist)>
<!ELEMENT Whitelist (Record)>
<!ELEMENT Blacklist (Record)>
<!ELEMENT Record ( Uri, Permission, FavouriteName)>
<!ELEMENT Uri (#PCDATA)>
<!ELEMENT Permission (#PCDATA)>
<!ELEMENT FavouriteName (#PCDATA)>

`ELEMENT <URIList>`

Element	`<!ELEMENT URIList (WapPush, Browser, PushEMail, DevPro)>`
Semantics	`<URIList>` is the root element. It should contain at least one of `<WapPush>`, `<Browser>`, `<PushEMail>`, or `<DevPro>` elements mandatorily.

`ELEMENT <WapPush>`

Element	`<!ELEMENT WAPPush (Whitelist, Blacklist)>`
Semantics	`<WapPush>` element indicates that the URIs being pre-configured are of `WapPush` service type. It should contain at least one of `<EBlackList>` or `<EWhiteList>` elements mandatority.

`ELEMENT <Browser>`

Element	`<!ELEMENT Browser (Whitelist, Blacklist)>`
Semantics	`<Browser>` element indicates that the URIs being pre-configured are of `Browser` service type. It should contain at least one of `<EBlackList>` or `<EWhiteList>` elements mandatorily.

`ELEMENT <PushEMail>`

Element	`<!ELEMENT PushEMail (Whitelist, Blacklist)>`
Semantics	`<PushEMail>` element indicates that the URIs being pre-configured are of `PushEMail` service type. It should contain at least one of `<EBlackList>` or `<EWhiteList>` elements mandatorily.

`ELEMENT <DevPro>`

Element	`<!ELEMENT DevPro(Whitelist, Blacklist)>`
Semantics	`<DevPro>` element indicates that the URIs being pre-configured are of `DeviceProvisioning` service type. It should contain at least one of `<EBlackList>` or `<EWhiteList>` elements mandatorily.

`ELEMENT <Whitelist>`

Element	`<!ELEMENT Whitelist (Record)>`
Semantics	`<Whitelist>` element indicates that the URIs being pre-configured should be whitelisted. It contains at least one `<Record>` element mandatorily.

`ELEMENT <Blacklist>`

Element	`<!ELEMENT Blacklist (Record)>`
Semantics	`<Blacklist>` element indicates the URIs being pre-configured should be blacklisted. It contains at least one `<Record>` element mandatorily.

`ELEMENT <record>`

Element	`<!ELEMENT Record ( Uri, Permission, FavouriteName)>`
Semantics	`<Record>` element contains the URI and its properties. It should contain mandatory element `<Uri>` and can optionally contain `<Permission>` and `<favouriteName>` elements. For each URI to be added to the URI List, one `<Record>` element should be created.

`ELEMENT <Uri>`

Element	`<!ELEMENT Uri (#PCDATA)>`
Semantics	`<Uri>` specifies the URI to be added to URI List. This should not be null. The URI format should be compliant with RFC 3986.

`ELEMENT <Permission>`

Element	`<!ELEMENT Permission (#PCDATA)>`
Semantics	`<Permission>` specifies the access level of `Uri`. It should be set to either “`EReadOnly`” or “`EReadWrite`”. The read-only URIs cannot be deleted or modified. If not specified by default, the access level of `Uri` is set to “`EReadWrite`”

`ELEMENT <FavouriteName>`

Element	`<!ELEMENT FavouriteName (#PCDATA)>`
Semantics	`<FavouriteName>` specifies the URI’s favourite name to be added to the URI List. This is an optional element.