All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hubert Chan <hubert@uhoreg.ca>
To: reiserfs-list@namesys.com
Subject: Re: [Fwd: filesystem support for XML storage and querying]
Date: Wed, 19 May 2004 14:49:55 -0400	[thread overview]
Message-ID: <874qqcfe0c.fsf@uhoreg.ca> (raw)
In-Reply-To: 40AC1B2E.7050807@namesys.com

>>>>> "Hans" == Hans Reiser <reiser@namesys.com> writes:

Hans> This was a good paper.:)

Thank you. :)

Hans> I don't understand the notion of ids, what motivates them, etc.

They are used in XML query engines for such things as removing duplicate
results.  (Although, I suppose inode number, or something similar, would
work just as well for this.)

Also, since XML nodes don't have names, we need to assign some sort of
ID so that they can be referenced in some way.  (e.g. if you have a
DocBook document with several chapters, you have to be able to tell the
filesystem which chapter you want to edit/remove/etc.)  Assigning each
node a persistent ID seems to be the simplest way to do things.

Hans> ReiserFS originally intended to use unique ids and then we
Hans> realized that keys were better.

I'm not familiar with what you mean by keys vs. ids, but it is possible
that using keys would be better.


As I said before, that paper is just a proposal, and I may or may not
actually implement it.  So unless I specifically re-claim it, that
topic is up for grabs for anyone who's interested.

-- 
Hubert Chan <hubert@uhoreg.ca> - http://www.uhoreg.ca/
PGP/GnuPG key: 1024D/124B61FA
Fingerprint: 96C5 012F 5F74 A5F7 1FF7  5291 AF29 C719 124B 61FA
Key available at wwwkeys.pgp.net.   Encrypted e-mail preferred.


      reply	other threads:[~2004-05-19 18:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1084953972.14831.3.camel@pear.st-and.ac.uk>
2004-05-20  2:42 ` [Fwd: filesystem support for XML storage and querying] Hans Reiser
2004-05-19 18:49   ` Hubert Chan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874qqcfe0c.fsf@uhoreg.ca \
    --to=hubert@uhoreg.ca \
    --cc=reiserfs-list@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.