From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20120815212734.GA1190@polynum.com> References: <20120803171847.GA2720@polynum.com> <501D12A1.1060906@yahoo.fr> <20120804152016.GB433@polynum.com> <20120805173639.GA395@polynum.com> <20120815173327.GA424@polynum.com> <20120815200949.4628BB85B@mail.bitblocks.com> <20120815212734.GA1190@polynum.com> Date: Thu, 16 Aug 2012 20:02:52 +0300 Message-ID: From: Eugene Gorodinsky To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=f46d04083adb9b2ef404c765037a Subject: Re: [9fans] Multi-dimensional filesystem Topicbox-Message-UUID: aa4c7db0-ead7-11e9-9d60-3106f5b1d025 --f46d04083adb9b2ef404c765037a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > > First one, related to what I was wandering about, is mathematical > definitions and relationships. Take the picture of the first volume of > van der Waerden's Albebra (I have the german edition and will keep the > german words). We speak about links between notions presented in a > linear order: the order of the chapters: > > Galois theory chapter is the descendant of concepts from > Vektorr=C3=A4ume, Fortsetzung der Gruppentheorie and K=C3=B6rpertheorie c= hapters; > Vektorr=C3=A4ume and Gruppentheory being siblings ("children" of Ringe un= d > K=C3=B6rper) while K=C3=B6rpertheorie is a grand-child of Vektorr=C3=A4um= e. > > Example of multiple parents, and not at the same level. > > This seems to be possible to recreate with befs, but I have to say: this particular problem is too specific to be solved with something like a filesystem. One should write a fileserver only when that would allow the user to use multiple familiar tools to work on the task. With your example it looks like the only thing the user would need here is the list of related topics along with the description of their relationship so that a related topic could be chosen and read. You can use a relational database for storage of the content along with the list of related topics and a program that can browse that database and follow the links. A user would never even think about doing something like 'cp ./Galors theory/parents ./Galors theory/children, even though the approach of implementing that in a fileserver allows that. --f46d04083adb9b2ef404c765037a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
First one, relate= d to what I was wandering about, is mathematical
definitions and relationships. Take the picture of the first volume of
van der Waerden's Albebra (I have the german edition and will keep the<= br> german words). We speak about links between notions presented in a
linear order: the order of the chapters:

Galois theory chapter is the descendant of concepts from
Vektorr=C3=A4ume, Fortsetzung der Gruppentheorie and K=C3=B6rpertheorie cha= pters;
Vektorr=C3=A4ume and Gruppentheory being siblings ("children" of = Ringe und
K=C3=B6rper) while K=C3=B6rpertheorie is a grand-child of Vektorr=C3=A4ume.=

Example of multiple parents, and not at the same level.

This seems to be possible to recreate with befs, but = I have to say: this particular problem is too specific to be solved with so= mething like a filesystem. One should write a fileserver only when that wou= ld allow the user to use multiple familiar tools to work on the task. With = your example it looks like the only thing the user would need here is the l= ist of related topics along with the description of their relationship so t= hat a related topic could be chosen and read. You can use a relational data= base for storage of the content along with the list of related topics and a= program that can browse that database and follow the links. A user would n= ever even think about doing something like 'cp ./Galors theory/parents = ./Galors theory/children, even though the approach of implementing that in = a fileserver allows that.

--f46d04083adb9b2ef404c765037a--