Implementing YADIS with no new software

[Christopher E. Granade]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Benjamin Yu wrote:
> For those that are unfamiliar with RDF, just think it as a bunch of Statements
> formed as: Subject Predicate(Property) Object. Where Object is either another
> Subject or a Literal String. All Subjects (aka Resources) and Predicates are
> URI identified. Thus, a collection of Statements can form a graph of
> descriptive meta-data.
> 
> -Ben
Thanks for the summary! As I said, I'm none too familiar with RDF- I
suggested it because it seems to work well for things such as Creative
Commons licenses, which can almost be visualized as another
"capability": they have a distinct URL that associates with a Work (in
the case of YADIS, a Consumer). Furthermore, the use of the rel="meta"
construction seems to have a fairly wide basis, being recommended for CC
and Dublin Core metadata. Other formats, like RSS, incorporate RDF
directly into the schema, allowing for RDF+CC/DC/YADIS (RCDY?) to be
embedded directly, or included via XInclude or an XSL stylesheet.

I must say that in recent months, programs like xsltproc have made an
XML-lover out of me- not because XML itself is so wonderful, but because
it is a well-understood standard with lots (and I do mean lots) of
developer support available. Seems to me, why reinvent the wheel? RDF
seems like it was designed- or at least is widely used- for exactly this
kind of purpose, and that mechanisms exist to couple RDF to arbitrary
XML documents.

- --Chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFDZnT00dXuuZr00J4RAvhGAKDvAOBcuGPJNKhvr2AThjvzNzPgCACePSiJ
k2CsUCKwF9bMAvEzM/vbTc4=
=efgK
-----END PGP SIGNATURE-----