Common items for the catalog

Hello implementors,
In the RetailOrder.xsd schema, a Catalog is defined as an element
containing a list of CatalogItems.  This catalog must be returned by a
call to any of our implementations of Retailer.getCatalog() operation
(see the Retailer.wsdl).  Here is the definition of CatalogItem in the
RetailerOrder.xsd.

<xsd:complexType name="CatalogItem">
		<xsd:sequence>
			<xsd:element name="name"          type="xsd:string" minOccurs="1"
maxOccurs="1"/>
			<xsd:element name="description"   type="xsd:string" minOccurs="1"
maxOccurs="1"/>
			<xsd:element name="productNumber" type="tns:productNumber"
minOccurs="1" maxOccurs="1"/>
			<xsd:element name="category"      type="xsd:string" minOccurs="1"
maxOccurs="1"/>
			<xsd:element name="brand"         type="xsd:string" minOccurs="1"
maxOccurs="1"/>
			<xsd:element name="price"         type="xsd:decimal" minOccurs="1"
maxOccurs="1"/>
		</xsd:sequence>
	</xsd:complexType>

What I propose is that we come up with a list of a few common items. 
Although it will be useful for each implementor to have a list of unique
items.  It will also be useful, I believe, for us to have common items
so that we can show distributed inventory management (not necessarily so
much in this demo, but when we add support for transactions).  Basically
an implementor would return, at a minimum, this list of catalog items. 
Each implementor may change a few details of the catalog items.  For
example the description, and the price. However, product numbers MUST be
unique across all implementations and thus for each productNumber,
category, brand and name must match.  
I have attached an xml file with some proposed items that can be the
default list.  Again, it is encouraged that once we agree on a default
list, that each implementer has more items than the default.  Please
take a look at the catalog items and comment on whether they should be
the default or if you would prefer there be no default.

Cheers,
Simeon