RE: [wsdm] blackberry schema still has issues in latest interop doc

["Sedukhin, Igor S" <Igor.Sedukhin@ca.com>]

That is right. I was waiting for the correct schema as I had no time to
pay attention to it. So eventually I published the doc with what I had.

I can paste your schema, but I'd rather have it confirmed by the
providers of the Blackberry...


-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749

-----Original Message-----
From: Springer, Ian P. [mailto:ian.springer@hp.com] 
Sent: Monday, April 04, 2005 5:32 PM
To: wsdm@lists.oasis-open.org
Subject: [wsdm] blackberry schema still has issues in latest interop doc

None of the properties defined in the blackberry schema (section 9.1)
are valid metrics (i.e. they don't extend the MUWS metric attribute
group). They are all defined as simple types. This conflicts with the
Blackberry metrics act, which refers to five of them as metrics
properties.

I think a corrected version of the schema should look something like:

<xs:schema targetNamespace="http://pda.rim";
           xmlns:tns="http://pda.rim";
           xmlns:xs="http://www.w3.org/2001/XMLSchema";>

   <xs:import
namespace="http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-part2.
xsd" 
 
schemaLocation="http://docs.oasis-open.org/wsdm/2004/12/muws/wsdm-muws-p
art2.xsd"/>

   <xs:element name="time"> 
	<xs:complexType> 
		<xs:sequence> 
			<xs:element name="hour" type="xs:int"/> 
			<xs:element name="minute" type="xs:int"/> 
		</xs:sequence> 
	</xs:complexType> 
   </xs:element>

   <xs:element name="date"> 
	<xs:complexType> 
		<xs:sequence> 
			<xs:element name="month" type="xs:int"/> 
			<xs:element name="day" type="xs:int"/> 
			<xs:element name="year" type="xs:int"/> 
		</xs:sequence> 
	</xs:complexType> 
   </xs:element>

   <xs:element name="BatteryStatus" type="xs:string" />
 
   <xs:complexType name="IntMetric">
		<xs:simpleContent>
			<xs:extension base="xs:int">
				<xs:attributeGroup
ref="muws-xs2:MetricAttributes"/>
				<xs:anyAttribute namespace="##other"
processContents="lax"/>
			</xs:extension>
		</xs:simpleContent>
   </xs:complexType>

   <xs:complexType name="StringMetric">
		<xs:simpleContent>
			<xs:extension base="xs:string">
				<xs:attributeGroup
ref="muws-xs2:MetricAttributes"/>
				<xs:anyAttribute namespace="##other"
processContents="lax"/>
			</xs:extension>
		</xs:simpleContent>
   </xs:complexType>

   <xs:element name="BatteryLevel" type="tns:StringMetric" />
   <xs:element name="AllocatedStorage" type="tns:IntMetric" />
   <xs:element name="FreeStorage" type="tns:IntMetric" />
   <xs:element name="TotalCodeModuleSize" type="tns:IntMetric" />
   <xs:element name="TotalStorage" type="tns:IntMetric" />

</xs:schema>


Note, I didn't define the date, time or BatteryStatus properties as
metrics, since IMO they make more sense as non-metric properties. Taking
this into account, the second part of the Blackberry Metrics Act would
need to be reworded as follows:

2.	Using the same EPR:
	a.	retrieve the muws-xs2:CurrentTime property;
	b.	retrieve the bbry:BatteryLevel, bbry:AllocatedStorage,
bbry:FreeStorage, bbry:TotalCodeModuleSize, and bbry:TotalStorage metric
properties and verify that MUWS metrics attributes are set (i.e. verify
that any of the muws-xs2:ResetAt or muws-xs2:Duration or
muws-xs2:LastUpdated attributes are set).


Ian

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in
OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php