- From: Borut Bolčina <bob@najdi.si>
- Date: Mon, 26 Sep 2005 16:16:08 +0200
- To: xmlschema-dev@w3.org
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
Received on Tuesday, 27 September 2005 03:31:05 UTC