OSB 10gR3, XSD's, namespaces, etc

Question

I have 2 questions here - they're pretty intertwined, so if one is answered it may answer the other.
1)
When an xml schema defines a namespace as follows: xmlns:ci="http://test.com/temp/customerinfo"
Why does OSB seem to ignore the "ci" and switch it to "cus"?
2)
I have 2 simple XSD's. The first XSD defines the main elements, and the second one defines the smaller elements.
<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ci="http://test.com/temp/ci" xmlns:temp="http://test.com/temp/temp" xmlns:fi="http://test.com/temp/fi" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://test.com/temp/temp" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import schemaLocation="default/test1" namespace="http://test.com/temp/ci" />
<xs:element name="portfolio">
<xs:complexType>
<xs:sequence>
<xs:element ref="ci:owner" />
<xs:element minOccurs="0" ref="ci:account" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
and
<?xml version="1.0" encoding="utf-8" ?>
<xs:schema xmlns:ci="http://test.com/temp/ci" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://test.com/temp/ci" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="owner">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="name" type="xs:string" />
<xs:element minOccurs="0" name="email" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="account">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="number" type="xs:string" />
<xs:element minOccurs="0" name="opendate" type="xs:string" />
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Here's a picture of what I'm seeing in the SBConsole:
[http://i39.tinypic.com/2rcnczn.jpg]
It looks like minOccurs="0" cannot be used. Is this correct, or is something else going on?
Here's the XML I'm driving with:
<?xml version="1.0" encoding="utf-8"?>
<temp:portfolio xmlns:temp="http://test.com/temp/temp" xmlns:ci="http://test.com/temp/ci"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ci:owner>
<ci:name>Timmy</ci:name>
<ci:email>[email protected]</ci:email>
</ci:owner>
<ci:account>
<ci:number>3442</ci:number>
<ci:opendate>1900-01-01</ci:opendate>
</ci:account>
</temp:portfolio>
Unless I link the Proxy Service to the 2nd XSD, I cannot get the xquery condition editor to actually return "true" to the following code:
$body/temp:portfolio/ci:owner/ci:name='Timmy'
Is there something wrong with my xsd?

Answer 1

1. In some situations OSB respects prefix and in others it doesn't. Anyway, don't care about namespace prefixes, they aren't important.
2a. You can use minOccurs="0" as you wish. There is nothing wrong on your example. The question mark in your screenshot simply tells you that some elements shouldn't be presented which is exactly what minOccurs="0" stands for.
2b. $body/temp:portfolio/ci:owner/ci:name='Timmy' can't be true.
Try $body/temp:portfolio/ci:owner/ci:name/text()='Timmy' instead.