[SM3] SM3 Meeting Minutes - 10 Mar, 2014.

[SM3] SM3 Meeting Minutes - 10 Mar, 2014.

[SM3] SM3 Meeting Minutes - 10 Mar, 2014.

Manchala, Daniel Daniel.Manchala at xerox.com
Mon Mar 10 21:38:03 UTC 2014


Meeting Attendees:

Rick Yardumian (Canon)
Bill Wagner (TIC)
Norbert Schade (Conexant)
Daniel Manchala (Xerox)


The Working Group discussed some inconsistencies in the SM schema pointed out by Norbert. Here are some of them that need to be corrected (or improved) - particularly the schema elements defined in the Scan Service. 


ScanService.xsd has the following element definition for "ImageBox".
===============

<xs:element name="ImageBox">
	<xs:complexType>
		<xs:sequence>
			<xs:element name="Height" type="RangeOfIntType"/>
			<xs:element name="Width" type="RangeOfIntType"/>
			<xs:element name="XOffset" type="RangeOfIntType" minOccurs="0"/>
			<xs:element name="YOffset" type="RangeOfIntType" minOccurs="0"/>
			<xs:element name="ContentRegionUnits">/* This needs to be changed to "RegionUnits" */
				<xs:complexType>
					<xs:sequence>
						<xs:element name="AllowedValues" type="ContentRegionUnitsType" maxOccurs="unbounded"/>		/* May need to be changed to "RegionUnitType */			
					</xs:sequence>
				</xs:complexType>
			</xs:element>
			<xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
		</xs:sequence>
	</xs:complexType>
</xs:element>



The element name "ContentRegionUnits" may need to be replaced with "RegionUnits" as a comparison with
PwgCommon.xsd will reveal.
=============

<xs:complexType name="ContentRegionType">
	<xs:sequence>
		<xs:element ref="pwg:Height"/>
		<xs:element ref="pwg:Width"/>
		<xs:element ref="pwg:XOffset" minOccurs="0"/>
		<xs:element ref="pwg:YOffset" minOccurs="0"/>
		<xs:element ref="RegionUnits"/> /* This is correct. It was called "ContentRegionUnits" in ScanService.xsd */
		<xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>
	<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>


Likewise, a similar change may need to be performed in the PwgWellKnownValues.xsd
                                                           =======================
<xs:simpleType name="ContentRegionUnitWKV"> /* This needs to be changed to "RegionUnitsWKV" */
	<xs:restriction base="xs:NMTOKEN">
		<xs:enumeration value="Other"/>
		<xs:enumeration value="Unknown"/>
		<xs:enumeration value="TenThousandthsOfInches"/>
		<xs:enumeration value="Micrometers"/>
		<xs:enumeration value="Pixels"/>
		<xs:enumeration value="Percent"/>
	</xs:restriction>
</xs:simpleType>


------------------ Allow multiple objects with same type.

Certain Scan Service elements can be enhanced to allow multiple objects with same type to be available in the service. For example, there could be two ADFs (ADF-upper and ADF-side) of the same type (ADF) on the same device / service. In order to do this, Norbert suggested adding an ID or make it extensible (via "any namespace=##other").

What we have in ScanService.xsd and what may need to be added.
                ================

<xs:element name="InputSource" minOccurs="0">
	<xs:complexType>
		<xs:sequence>
			<xs:element name="AllowedValues" type="InputSourceType" maxOccurs="unbounded"/>
			<xs:element name="ID" type="InputSourceType" maxOccurs="unbounded" /> /* This needs to be added */
		</xs:sequence>
	</xs:complexType>
</xs:element>


Likewise, another element that needs to be modified is DocumentFormat (allowing not only different formats for scan capture viz. PDF, TIFF, PwgRaster, etc., but also allowing different versions of a format viz. TIFF1, TIFF2, etc).

<xs:element name="DocumentFormat" minOccurs="0">
	<xs:complexType>
		<xs:sequence>
			<xs:element name="AllowedValue" type="DocumentFormatType" maxOccurs="unbounded"/>
			<xs:element name="ID" type="DocumentFormatType" maxOccurs="unbounded" /> /* This needs to be added */		</xs:sequence>
	</xs:complexType>
</xs:element>



------------------Question on the need to replace InputSourceType.
Bill mentioned that it was discussed in the IPP Scan meeting there was a need to replace InputSourceType with some other element that captures the characteristics of input sources other than ADF, Platen, etc., and which also takes other elements such as scanner resolution, encoding, etc. Ira/Mike might know this better.











More information about the sm3 mailing list