OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

relax-ng-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: [relax-ng-comment] Re: RelaxNG Schema for RSS 1.0 Core


There's a typo in one of the dc namespace URIs in dc.rng and test.rss (one
has a trailing #, one doesn't).  When this is fixed, test.rss does not
validate against dc.rng.

----- Original Message -----
From: "Joseph Reagle" <reagle@mit.edu>
To: "James Clark" <jjc@jclark.com>; "MURATA Makoto" <mmurata@trl.ibm.co.jp>
Cc: <relax-ng-comment@lists.oasis-open.org>
Sent: Thursday, September 19, 2002 11:44 PM
Subject: Fwd: RelaxNG Schema for RSS 1.0 Core


>
> The thing I *most* want to do with a schema language is define an
extensible
> structure, and then permit others to define their extensions which can
then
> be validated. I tried to do this below but failed, and suggestions?
>
> ----------  Forwarded Message  ----------
>
> Subject: RelaxNG Schema for RSS 1.0 Core
> Date: Wed, 18 Sep 2002 18:24:37 -0400
> From: Joseph Reagle <reagle@mit.edu>
> To: rss-dev@yahoogroups.com
>
> Friends, you can find my first stab at a RelaxNG Schema for RSS 1.0 Core
>  at:
>
> http://www.w3.org/2002/09/rss-rng/
>  rss.rng -- validates the core with extensible item content
> models quiet nicely.
>  dc.rng -- a working extension of the rss.rng schema that
> attempts but fails to constrain elements in the
> namespace associated with the dc:prefix .
>  test.rss -- an rss instance I tested the above with
>
> Presently, what I'm trying to do with dc.rng is beyond my relanxNG kung-fu
> (or not possible?). I'd like the dc:BAD element in the excerpt from
> test.rss to cause a failure when validated with dc.rng:
>
>   <item rdf:about="http://xml.com/pub/2000/08/09/xslt/xslt.html";>
>     <title>Processing Inclusions with XSLT</title>
>     <link>http://xml.com/pub/2000/08/09/xslt/xslt.html</link>
>     <description>
>      Processing document inclusions with general XML tools can be
>      problematic. This article proposes a way of preserving inclusion
>      information through SAX-based processing.
>     </description>
>     <dc:publisher>Example.com</dc:publisher>
>     <dc:creator>Joseph Reagle</dc:creator>
>     <dc:BAD>Joseph Reagle Jr.</dc:BAD> <!-- it'd be nice if dcc.rng choked
> on this -->
>     <dc:date>2002-09-18T18:00+00:00</dc:date>
>     <foo xmlns="http://example.org/foo";>bar</foo>
>   </item>
>
>
>



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC