From: Hans Reiser <reiser@namesys.com>
To: "John D. Heintz" <jheintz@pobox.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Do xml-like namespaces make sense for Reiser4? (re: metas thread)
Date: Mon, 12 Apr 2004 11:15:27 -0700 [thread overview]
Message-ID: <407ADCBF.8000609@namesys.com> (raw)
In-Reply-To: <407AB9AE.3060801@pobox.com>
Mhy colon instead of / ?
There is no reason for it. Implementing a storage layer to make XML
storage more efficient might be commercially interesting, but XML is not
what we should copy for namespace style.
Hans
John D. Heintz wrote:
> Hi all,
>
> I work with XML quite a lot in my job and deal with XML namespaces
> often. While I think they have some problems in the XML world (poor
> integration with XML InfoSet) they might be useful for Reiser4 and
> they seem to play well with the Set Theoretic underlying models (as
> far as I can tell :).
>
> Here's what I'm thinking:
> Instead of `cat foo.txt/metas/uid`
> it would be `cat foo.txt/reiser4:metas/uid` or perhaps `cat
> foo.txt/reiser4:uid`.
>
> Here the "reiser4" shorthand would map to "http://www.namesys.com/v4"
> or whatever Hans and team decided.
>
> The reiser4 namespace could be hardcoded or compiled in and exposed
> via `cat /proc/fs/reiser4/namespace`.
>
> Other namespaces could be added to files/directories and I'd assume
> something like:
> `cat foo.txt/reiser4:namespaces` would list all the namespaces
> available for a particular file.
> Something like:
> reiser4 http://www.namesys.com/v4
> streams http://www.evil-empire.com/streams
> snapcm http://www.snapcm.com/snapcm
>
> John D. Heintz
>
> ps - SnapCM is the name of a versioned linking model that I developed
> some time ago and hope one day to build a plugin for Reiser4. I'm
> being optimistic listing it in the available namespaces. ;-)
>
>
--
Hans
next prev parent reply other threads:[~2004-04-12 18:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-12 15:45 Do xml-like namespaces make sense for Reiser4? (re: metas thread) John D. Heintz
2004-04-12 16:00 ` Hubert Chan
2004-04-12 19:21 ` John D. Heintz
2004-04-12 21:28 ` Hubert Chan
2004-04-12 18:15 ` Hans Reiser [this message]
2004-04-12 18:59 ` Hubert Chan
2004-04-12 19:12 ` John D. Heintz
2004-04-13 14:40 ` John D. Heintz
2004-04-13 16:31 ` Hans Reiser
2004-04-13 16:57 ` John D. Heintz
2004-04-13 17:06 ` Grant Miner
2004-04-13 18:09 ` John D. Heintz
2004-04-13 18:36 ` Grant Miner
2004-04-13 17:47 ` Hans Reiser
2004-04-13 18:23 ` John D. Heintz
2004-04-13 18:28 ` Hans Reiser
2004-04-13 18:47 ` John D. Heintz
2004-04-13 20:31 ` Valdis.Kletnieks
2004-04-14 2:18 ` Enrique Perez-Terron
2004-04-14 15:06 ` John D. Heintz
2004-04-14 23:39 ` Enrique Perez-Terron
2004-04-14 2:50 ` David Masover
2004-04-14 15:12 ` John D. Heintz
2004-04-15 0:28 ` David Masover
2004-04-15 15:15 ` John D. Heintz
2004-04-16 1:04 ` David Masover
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=407ADCBF.8000609@namesys.com \
--to=reiser@namesys.com \
--cc=jheintz@pobox.com \
--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.