<xsd:simpleType name="standardChannelPropertyName.type">
<xsd:annotation>
<xsd:documentation>Standard channel property name http://www.w3.org/TR/InkML/#channelProperty</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<!-- Threshold - e.g. for a binary channel, the threshold force at which the tip switch is activated -->
<xsd:enumeration value="threshold"/>
<!-- Resolution - the scale of the values recorded. This may be expressed as fractions of a unit, e.g. 1/1000 in (inches), 0.1 mm, 1 deg (degrees). It may also be expressed, more more popularly, in inverse units, e.g. "1000 points per inch" would be given as 1000 in units 1/in.-->
<xsd:enumeration value="resolution"/>
<!-- Quantization - the unit of smallest change in the reported values. If the value is reported as integer, this is assumed to be the same as the resolution. Note that if decimal values are recorded for resolution, the quantization of the data may be smaller than the "resolution"-->
<xsd:enumeration value="quantization"/>
<!-- Noise - the RMS value of noise typically observed on the channel. This is distinct from accuracy! It is an indication of the difference observed in the data from the device when the same path is traced out multiple times (e.g. by a robot)-->
<xsd:enumeration value="noise"/>
<!-- Accuracy - the typical accuracy of the data on the channel (e.g. "0.5 mm", "10 degrees" or "0.1 newton") This is the typical difference between the reported position and the actual position of the pen tip (or tilt ...)-->
<xsd:enumeration value="accuracy"/>
<!-- Cross-coupling - the distortion in the data from one channel due to changes in another channel. For example, the X and Y coordinates in an electromagnetic digitizer are influenced by the tilt of the pen. This would be specified by dX/dOTx = ... or max delta X vs. OTx = ... If the influencing channels are also recorded, and the cross-couplings are accurately specified, it may be possible to compensate for the cross-coupling by subtracting the influence, at the expense of higher noise. The cross-coupling is always expressed in the units of the two channels, e.g. if X mm and OTx is in degrees, then cross-coupling is in mm/deg.-->
<xsd:enumeration value="crossCoupling"/>
<!-- Skew - the temporal skew of this channel relative to the basic device latency, if any. For example, some devices actually sample X and Y at different points in time, so one might have a skew of -5 millisecond, and the other +5 millisecond.-->
<xsd:enumeration value="skew"/>
<!-- Minimum bandwidth (in Hz) - the minimum bandwidth of the channel, in Hz (not samples/second), i.e., the frequency of input motion up to which the signal is accurate to within 3dB.-->
<xsd:enumeration value="minBandwidth"/>
<!-- Peak rate - the maximum speed at which the device can accurately track motion-->
<xsd:enumeration value="peakRate"/>
<!-- Dynamic distortion, e.g., how velocity affects position accuracy. This is expressed in inverse seconds, e.g. 0.01 mm / mm / s. This kind of distortion is often cross channel, but this specification only allows a generic, channel-specific value.-->
<xsd:enumeration value="distortion"/>
</xsd:restriction>
</xsd:simpleType> |