[sitemap] Syntax Proposal
- I'm coming forward with a proposal to add a site map module to
RSS 1.0, as a continuation of the earlier thread I started
regarding site maps. I'm hoping that describing some syntax
may help jump start the conversation.
The syntax is based on the earlier "proto-RDF" site map syntax
that was supported by early builds of Mozilla, samples of which
are still available at these urls:
The Site Map module would consist of three elements, <map>,
<topic>, and <child>. The child entries would point to the RSS
<item> resources. Assuming that the sitemap module would
use the "sm" namespace prefix, here's a simple example of the
syntax (watch out for wrapping):
<sm:topic id="root" sm:name="rss-dev"
<sm:topic id="messages" name="Messages">
<sm:topic id="files" name="Files">
This is just a starting point, from someone who is still learning
how RDF and RSS work. I welcome any and all criticism :)
The foot can split wood, but it can't split a watermelon.
- -----BEGIN PGP SIGNED MESSAGE-----
On Mon 26-Feb-2001 at 08:32:42 -0000, dweingart@... wrote:
> This is just a starting point, from someone who is still learning
> how RDF and RSS work. I welcome any and all criticism :)
I've been thinking about this issue tonight as well, however I'm
still learning to the extent that I'm not even going to attempt to
write my ideas in RDF format :-)
I think that it might make sense to do a combined sitemap / thread
module as it could be used to describe Slash type sites, email
archives and sitemaps.
I think we need to be able to specify both parents and children, I'm
not sure why any other descriptions would be needed.
A RSS file describing a whole site would only need to name each
documents parent or it's children. I can't think of a good reason
for doing one rather than the other.
A RSS file that does not describe an entire site would need to have
the ability to name each documents parents and it's children.
I'm going to stop there, before I get carried away and start writing
about orphans, illegitimate relationships, adoptions and immaculate
Perhaps it should be a relationship module?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org
-----END PGP SIGNATURE-----
- dweingart@... <dweingart@...> wrote:
> The syntax is based on the earlier "proto-RDF" site map syntaxThis (Netscape's) syntax seems to be based on a very old draft of RDF, and
> that was supported by early builds of Mozilla, samples of which
> are still available at these urls:
so seems a bit quaint to my eyes. Your syntax however, seems to have brought
it up-to-date, although it does have a few problems (the IDs, for example).
Anyway, I'd like to second the suggestion of a simplified model for just a
list of parents and children. I think that would simplify things (for me at
least) quite a bit. However, that does leave us to deal with your concept of
a "topic" versus who knows what else the rest are (items, I guess). So
perhaps we can create a new property? (q:type = topic) Or maybe we can use
the taxo module to create topic and attach to those...
I just think this syntax is a bit hard to follow and doesn't really take
advantage of RSS as much as it could.
[ Aaron Swartz | me@... | http://www.aaronsw.com ]