|
 |
online DocBrowser for netUpdate_def.xsd
Version: |
1.00 |
Generation Date: |
1 May 2003 |
|
|
 |
|
Element product
name |
data type |
content |
product |
- |
empty |
product defines the product in terms of the name, error communication, and URL for accessing the update information (cf. the netUpdate_upd.xsd schema file). |
 |
subelements in the requested order |
|
none |
|
 |
|
attribute name |
data type |
[min,max] |
default |
|
ean |
pattern |
[1,1] |
- |
|
ean=(76[0-9]{11}) is the official EAN number of the company (global identification number in official EAN lingua) being responsible for the product. This EAN number and the base URL is checked dynamically on the TMR site against a registration database prior to any update process. |
|
email |
pattern |
[1,1] |
- |
|
email=(.+@.+) is the email address to which an error report is automatically sent if and only if an error occurs during the update process that is related to the data or web services for that product. That is if an application error occurs, then this service is not activated. The primary motivation for this is to keep you as the owner of the software informed about possible problems. |
|
name |
string |
[1,1] |
- |
|
name supplies the name of the product. This name is displayed as entry in the netUpdate application. While not mandatory it is recommended to choose this name as part of the definition file name as well (e.g. name_dt.def for the german version of this product) |
|
url |
anyURI |
[1,1] |
- |
|
url is the absolute URL where to retrieve the update file. Note that one can submit local information like license keys by defining a approriate parameter and the using a http GET syntax for transporting that parameter to the netUpdate_updServer. Before sending out the request, the netUpdate application will expand the parameter to the correct value to help authenticate the user on the target update server. For instance such an URL can be written as: http://www.test.net/test/test.asp?UID=${UID} Please note that if a URL has more the just 1 parameter then the & between any to arguments -due the schema definition- must be escaped by the entity &! |
 |
|