- From: Reto Hermann <rhe@zurich.ibm.com>
- Date: Tue, 30 Apr 2002 15:40:32 +0200
- To: www-mobile Mailingliste <www-mobile@w3.org>
- Cc: Johannes Koch <koch@pixelpark.com>
Johannes -
the collection of profiles you assembled is very useful. I ran them against
my validating parser and found these glitches:
Alcatel_OTxxx.rdf:
wrong component type: SoftwareProfile (should be SoftwarePlatform)
wrong component type: HardwarePlatform (should be HardwarePlatform)
Trium_Eclipse.rdf:
mis-spelled property name: InputCharset (should be InputCharSet)
mis-spelled property name: OutputCharset (should be OutputCharSet)
wrong component type: PushCharacteristicts (should be
PushCharacteristics)
Motorola_xxxx.rdf, NEC_21i:
wrong component type: SoftwareProfile (should be SoftwarePlatform)
wrong component type: HardwarePlatform (should be HardwarePlatform)
Nokia _xxxx.rdf:
wrong component type: SoftwareProfile (should be SoftwarePlatform)
wrong component type: HardwarePlatform (should be HardwarePlatform)
Nokia _7650.rdf:
wrong component type: SoftwareProfile (should be SoftwarePlatform)
wrong component type: HardwarePlatform (should be HardwarePlatform)
invalid property value: 'unlimited' for property WmlDeckSize
Siemens_C35i.rdf, Siemens_S35.rdf
wrong component type: PushCharacteristicts (should be
PushCharacteristics)
wrong component type: WapCharacteristicts (should be
WapCharacteristics)
Siemens_S45.rdf:
wrong component type: SoftwareProfile (should be SoftwarePlatform)
wrong component type: HardwarePlatform (should be HardwarePlatform)
Ericsson_xxxx.rdf:
wrong component type: SoftwareProfile (should be SoftwarePlatform)
wrong component type: HardwarePlatform (should be HardwarePlatform)
Ericsson_R320.rdf:
invalid property value: '1x1.24' for property PixelAspectRatio
Ericsson_R380.rdf:
invalid property value: '??x7' for property ScreenSizeChar
Sony_CMD-Z5.rdf:
wrong component type: PushCharacteristicts (should be
PushCharacteristics)
wrong component type: WapCharacteristicts (should be
WapCharacteristics)
In addition to these, several profile documents contain XML elements
(representing scalar property values or collection items (rdf:li)) that are
empty. This may not be invalid, but certain parsers might throw up.
Hope this helps!
Cheers,
Reto Hermann
------------------------------------------------------------
IBM Zurich Research Laboratory
Saeumerstrasse 4
CH-8803 Rueschlikon mailto:rhe@zurich.ibm.com
Switzerland phone: +41-1-724 8479 fax: +41-1-724 8953
Johannes Koch
<koch@pixelpark. To: www-mobile Mailingliste <www-mobile@w3.org>
com> cc:
Sent by: Subject: XSLT for transforming UAProf 1.2.1 into 2.0
www-mobile-reque
st@w3.org
04/24/2002 12:27
PM
Please respond
to Johannes Koch
Hi there,
I wrote an XSLT stylesheet for transforming UA profiles according to
WAP-174_100-UAProf-20000621-a (WAP 1.2.1) into profiles according to
WAP-248-UAProf-20011020-a (WAP 2.0):
<http://pixels.pixelpark.com/~koch/uaprof/xsl/uaprof121to20.xsl>
Additionally, there are some profiles, that I produced from several
phone documentation papers by Nokia, Motorola, Ericsson, etc.
(<http://pixels.pixelpark.com/~koch/uaprof/>).
--
Johannes Koch . IT Developer
Pixelpark AG . http://www.pixelpark.com
Rotherstraße 8 . 10245 Berlin . Germany
phone: +49 30 5058 - 1288 . fax: - 1355
Received on Tuesday, 30 April 2002 10:01:36 UTC