[xsd-users] Using XSD with RDF

[Jose]

Boris,

I will try to test XSD with the RSS 2.0 schema you point out. Glancing at
the schema, do you see
anything that might cause XSD to malfunction ?

I am trying to familiarize with XSD before thinking of using it with RDF
schemas.

Thanks and regards,
Jose



On 1/31/06, Boris Kolpackov <boris at codesynthesis.com> wrote:
>
> Jose,
>
> Jose <jmalv04 at gmail.com> writes:
>
> > Before considering the RDF schema I would like to know whether XSD can
> > tackle parsing the RDF file as XML.
>
> You probably mean if XSD (the tool) can generate the code to parse
> RDF as an XML.
>
> > That by itself would make XSD very useful to me.  I imagine it's
> > possible but I am not sure
> >
> > Here is a sample for RSS RDF
>
> It is definitely possible if you can come up with an XML Schema
> definition for your RSS RDF. Looking at the instance below it looks
> very similar to an RSS instance with RDF extensions. There is an
> XML Schema for RSS 2.0 available:
>
> http://www.thearchitect.co.uk/schemas/
>
> hth,
> -boris
>
> > <?xml version="1.0" encoding="utf-8"?>
> > <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> >  xmlns:dc="http://purl.org/dc/elements/1.1/"
> >  xmlns:rss="http://purl.org/rss/1.0/"
> >  xmlns="http://purl.org/rss/1.0/">
> > <channel rdf:about="http://dig.csail.mit.edu/breadcrumbs/blog/4">
> >  <title>timbl's blog</title>
> >  <link>http://dig.csail.mit.edu/breadcrumbs/blog/4</link>
> >  <description></description>
> >  <items>
> >   <rdf:Seq>
> >   <rdf:li rdf:resource="http://dig.csail.mit.edu/breadcrumbs/node/72"/>
> >
> >   <rdf:li rdf:resource="http://dig.csail.mit.edu/breadcrumbs/node/71"/>
> >   <rdf:li rdf:resource="http://dig.csail.mit.edu/breadcrumbs/node/62"/>
> >   <rdf:li rdf:resource="http://dig.csail.mit.edu/breadcrumbs/node/54"/>
> >   <rdf:li rdf:resource="http://dig.csail.mit.edu/breadcrumbs/node/38"/>
> >   </rdf:Seq>
> >  </items>
> > </channel>
> > <item rdf:about="http://dig.csail.mit.edu/breadcrumbs/node/72">
> >  <title>Backward and Forward links in RDF just as important</title>
> >
> >  <link>http://dig.csail.mit.edu/breadcrumbs/node/72</link>
> >  <description>&lt;p&gt;&lt;em&gt;&lt;a
> > href="http://www.ctaz.com/~dmn1/hein.htm"&gt;Piet Hein&lt;/a&gt;, I
> > think, &lt;a href="http://chat.carleton.ca/~tcstewar/grooks/grooks.html
> "&gt;Grooked&lt;/a&gt;
> > that,&lt;/p&gt;
> >
> > &lt;p&gt;"Two types that had far better leave to their betters&lt;br
> /&gt;
> > the civilized art of exchanging letters&lt;br /&gt;
> > are those who disdain to make any response,&lt;br /&gt;
> > and those who infallibly answer at once!"&lt;/p&gt;
> > &lt;p&gt;The regularity of this blog fails on both
> counts.&lt;/em&gt;&lt;/p&gt;
> >
> > &lt;p&gt;One meme of RDF ethos is that the direction one choses for a
> > given property is arbitrary: it doesn't matter whether one defines
> > "parent" or "child"; "employee" or "employer". This philosophy (from
> > the Enquire design of 1980) is that one should not favor one way over
> > another.  One day, you may be interested in following the link one
> > way, another day, or somene else, the other way. &lt;/p&gt;
> > &lt;p&gt;On the other hand, also one should not encourage people
> > having to declare both a property and its inverse, which would simply
> > double the number of definitions out there, and give one more axis of
> > arbitrary variation in the way information is expressed. Therefore,
> > the design of the tabulator was is to make the system treat forward
> > and backward links equivalently.&lt;/p&gt;
> > &lt;p&gt;The design of &lt;a
> > href="http://www.w3.org/DesignIssues/Notation3"&gt;N3&lt;/a&gt; also
> > was influenced by this.  The ability to write&lt;/p&gt;
> >
> > &lt;p&gt;:Joe is f:parent of :Fred.&lt;/p&gt;
> > &lt;p&gt;makes it easier to write (or generate) N3 without having to
> > use f:child.  This in turn reduces the pressure to define
> > both.&lt;/p&gt;
> > &lt;p&gt;The only loss in not having both is that there is no label
> > for the reverse link. (In same cases I have defined an unnamed
> > predicate which is delcared as the inverse and has a label.)&lt;/p&gt;
> > </description>
> >  <dc:date>2006-01-25T16:21:17Z</dc:date>
> > </item>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (GNU/Linux)
>
> iQGVAwUBQ9+HOciAKQuuCE8dAQINRQv9FB1w793s6Vey9aV1EOjJI3+8Q8jh/+NS
> VhyIqs7StAYN0GZIIuuaMhvsezVMnwfwipLmYoSg6ao8C2bAAuQrbSBaI10lOyJ0
> RgdOqw2ibPp3zhw5CJx2Y4V/rlD5jd6BuzB0v5U41kACrQm/8LnksPs0LWzx8y7C
> wHqJ7GQEX2gx2G8S6SNnbaMSjUxttJaq0t3i8yyKqxR4DRk6k09Dk6kYhM2zHCQE
> afsredi8RPkaBUyJDSODVqpEex8uXKJ/UxvLFTavt2PttTahu63C5BVHO4VexvRS
> mF8yMs7b4PRtG//turKxHnHy8MkDY1LujBhr6LQleYQDBu5JfKLsIjF5SSwXj0BJ
> QrQBv+Vpi1C5KtYi1XE9kgeTjG3knRxxD0VR3AhTPUol8aQgebNubbVTM8nnhLU6
> CrRLh7fNc/1Rk00FKYRgc0eGPkGyE/4yjAgaoIlpVlzkQMGyAuxXfFvKmq2Sf+IE
> T/n0QQSpSwpxXjktv0TJmd2h5K6LF0+j
> =z/Wz
> -----END PGP SIGNATURE-----
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://codesynthesis.com/pipermail/xsd-users/attachments/20060131/3f6bdd26/attachment.htm