Re: Extending RSS 2.0

Michael thanks, but if I do this

<rss version="2.0" xmlns:job="http://schema.noviforum.si/job" 
job:schemaLocation="path/to/job.xsd" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:noNamespaceSchemaLocation="http://www.thearchitect.co.uk/schemas/rss-2_0.xsd">

then XMLSpy says:
The file is not valid: Although matched by wildcard job:schemaLocation, 
no declaration can be found for attribute '(null').

-bb

On 27.9.2005 9:56, Michael Kay wrote:

>Because the wildcard uses processContents="lax", the validator will look for
>schema declarations for your namespace and validate against them if found.
>So you need to tell the validator where to find a schema for your namespace.
>You could do this using xsi:schemaLocation.
>
>Michael Kay
>http://www.saxonica.com/ 
>
>  
>
>>-----Original Message-----
>>From: xmlschema-dev-request@w3.org 
>>[mailto:xmlschema-dev-request@w3.org] On Behalf Of Borut Bolcina
>>Sent: 26 September 2005 15:16
>>To: xmlschema-dev@w3.org
>>Subject: Extending RSS 2.0
>>
>>
>>Hello,
>>
>>if I extend RSS 2.0 with some additional <item> elements in 
>>my own job: 
>>namespace like this:
>>
>><item>
>>    <title>Job title</title>
>>    <link>http://link/to/some/job</link>
>>    <description>Job description.</description>
>>    <enclosure url="http://some.domain.com/img/logo.jpg" 
>>type="image/jpeg" length="34566"/>
>>    <pubDate>Mon, 26 Sep 2005 11:25:10 +0200</pubDate>
>>    <job:company>Acme ltd.</job:company>
>>    <job:work-area>Job work area</job:work-area>
>>    <job:type>type of job</job:type>
>>    <job:education>level of education</job:education>
>>    <job:location region="some region">town</job:location>
>>    <job:expires>Mon, 17 Oct 2005 11:25:10 +0200</job:expires>
>></item>
>>
>>it validates perfectly ok with 
>>http://www.thearchitect.co.uk/schemas/rss-2_0.xsd. Understandably, as
>>
>><xs:any namespace="##other" processContents="lax" minOccurs="0" 
>>maxOccurs="unbounded">
>>    <xs:annotation>
>>        <xs:documentation>Extensibility element.</xs:documentation>
>>    </xs:annotation>
>></xs:any>
>>
>>is allowing this. Now, how do I enforce rules for my job: 
>>elements? The 
>>basis for validation would be the above xsd, which would 
>>allow inclusion 
>>of different new sets of elements and namespaces (one of them being 
>>job:, the other maybe commerce:).
>>
>>How to do this right?
>>
>>Regards,
>>Borut
>>
>>
>>
>>    
>>
>
>
>  
>