From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id uO3lGXh49mNFeAEAbAwnHQ (envelope-from ) for ; Wed, 22 Feb 2023 21:18:00 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id ILnkGXh49mP+4QAA9RJhRA (envelope-from ) for ; Wed, 22 Feb 2023 21:18:00 +0100 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id D488F3CF8E for ; Wed, 22 Feb 2023 21:17:59 +0100 (CET) Authentication-Results: aspmx1.migadu.com; dkim=none; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=none ARC-Seal: i=1; s=key1; d=yhetil.org; t=1677097080; a=rsa-sha256; cv=none; b=Lhd4PPDWT/+uebzEzUkWXffEpK2tadWJWdZ7g8TZ1wZs3Ao27Kj/mPRqvUiq7TqTRucHjb baI4DDaEod02+2Q6MUITrrzzof9qgPR4Li980G982DOQ3vDY43dVb4ZGgYz5BWvvdfBwYL vRLqKLR3SvDegUIBxmCAY7ryWZNIf6s6sY9+btM4epdQ6R1q48pwXdUfhwbSuptrbkH69t n6dw+sO7CRZbXNL63Cs6EpuZCszJ4IBEDKZr7BnFdZFh3bxZUVi3DIL47UsG9bmTIleqLP gHg8/zTQUbKYKIrbZ1vq6ShG2JD9gjz+D0f904jw7Mtdit8MMAG0KETNtsO8qw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1677097080; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=IC6dTnP3DSCPg/GQTAtjX0PtedDIhJjqRPBZhzJZ468=; b=sYvXHmzmEMiLrq0P+ZkYSfncRjYHWR+8JZk9HpJjeYceG38w1ULZg929ak6mKFD3UlXpBv zIjCgS+N/koQzCZbsPH3p+f2cA0wMzQZjJqMoxLIFECKX70r3kNfMPJrbTZEU4VkOw6zrf FoR9J0kDDLtV1CK9v5CCk2OD+rw4bpDSlHVEvfoyj7YGCKmMXXABGjQZGZ2Jeg8Uv8PUNe AgFqz6oSnxJwprVwdxc1QnMcc7uyS8UrYDiLzXYTTBGG60oUvKJI7A16U21l/roilMdRKd z3V2FVmCfK0N+il49ESFHN+lvcMh9cMxMQoPlUBaJeaQHPi9g7cXDrbCb5u6aQ== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pUvXy-00061A-DH; Wed, 22 Feb 2023 15:17:02 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pUvXs-0005zt-3Q for emacs-orgmode@gnu.org; Wed, 22 Feb 2023 15:16:56 -0500 Received: from stw1.rcdrun.com ([217.170.207.13]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pUvXp-0005It-EQ for emacs-orgmode@gnu.org; Wed, 22 Feb 2023 15:16:55 -0500 Received: from localhost ([::ffff:197.239.12.227]) (AUTH: PLAIN admin, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 0000000000103840.0000000063F6780F.0000024F; Wed, 22 Feb 2023 13:16:15 -0700 Date: Wed, 22 Feb 2023 22:30:06 +0300 From: Jean Louis To: Cletip Cletip Cc: Org Mode List Subject: Re: Link type in org-mode, but with org-roam ? Message-ID: Mail-Followup-To: Cletip Cletip , Org Mode List References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.2.9+54 (af2080d) (2022-11-21) Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: X-Migadu-Queue-Id: D488F3CF8E X-Spam-Score: -1.96 X-Migadu-Spam-Score: -1.96 X-Migadu-Scanner: scn0.migadu.com List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-TUID: CpNiwHwRBxI5 * Cletip Cletip [2023-02-21 19:20]: > I am not thinking in advance about "queryable" information. I am > > thinking of structure, or types, and do not worry of future. All > > types, columns, anything is automatically capable to be queried. Solely the above paragraph is not giving me enough information. It is general statement. In every Emacs buffer anything is automatically capable to be queried. One can search by using regular expressions and there is plethora of other ways to find information. Similarly one can tell that for many other systems. I find almost anything in any text by using `ed' the standard text editor. I am trying to understand what you mean with it, and it that is something that I have not described above. > I was talking about my system which was made with org-roam, so the > information stored in the notes is in plain text. But, to make them > queryable, I have to add "metadata" as said before with key-value. Okay, I understand. Meta data is normally not visible or can be made visible, but is not part of the text, but could be part of Org heading, like Org properties or tags. Including that all words and sentence can also be considered part of it. > So I'm using a database, but I don't want to bother thinking about > how I can add new information to my system. You, you need to think > about "what describes this information?" I cannot see practical example, so I cannot understand. I cannot even know if your description of what I think fits to what I think that I think... hmm, let me see. Do I really think about "What describes this information"? When I enter document in the Dynamic Knowledge Repository, then I name it. In that sense I think of "what describes this information", as I have to describe it, sort it, under some set, which is another way of describing it, maybe relate to people, and so on. However, when you write any text, you are "describing this information". I am trying to understand what you mean and how do you mean of doing things "without describing information". > If it's someone, you create a new table (not sure if this is this > term to use) to hold that knowledge. I don't want to think about > that, I just want to put the information in and find it without > thinking about tables. Yes, database system like GeDaFe is designed for user to create new table. Though that is not happening too often. If you only work with text, you need not special database, as your file system is enough. Org is prime example how text may be structured and mimic database features. > > Because of the design of tables, and conditional correct entries into > > the database, it becomes very easy to find for example "POST BOX" > > address of all people in Mwanza city. > > Here, everything is queryable, because you have already thought of > all the possible cases that could happen. In my system, I decided to > do the opposite: why think of a particular case if I'm not even sure > I'm doing it? It is true that by thinking in advance, one can get better results. For example, one starts creating separate table columns for: - first name - middle names - last name then I realized, people have nick names, what else, so I added another column like: - other names, as array that can hold any number of names then people have their titles, so you add "title" column. But then I realize people have different relationships, may have different roles in different organizations and thus different titles, so I added "people relationship" table, in which "titles" are described individually. And then how to search for that information? PostgreSQL full text search does that. Mastering PostgreSQL Tools: Full-Text Search and Phrase Search - Compose Articles: https://compose.com/articles/mastering-postgresql-tools-full-text-search-and-phrase-search/ So then anything may be queried with simple search, as long as all those fields are updated for full text search: Possible queries could be: - baker in Monaco - Joe, baker - Joe director Monaco and so on, and they could lead to same person. > But our goals are not the same, you have to have a solid system for > several people, I do something much more personal. So, it's ok. I will understand when you show me example. > I wanted to say that adding a new type of information can be time > consuming: you have to add the table, and above all check that > another table does not already exist to do the same thing. That is not time consuming: - adding new table is maybe 1 minute - I never check if other table do the same thing, but I could start making new table to improve previous work Adding tables is rapid on my side. > So you need excellent documentation, hoping that the system itself > doesn't become too "cluttered" for the user. I need documentation, I have little of it. It is just as Org, it needs a lot of documentation for people to use it. > For your purpose, yes. For mine, no. I think that every thing that > has to have a special presentation / type in the database is an > exception: the user has to think / look that, if he wants to add a > contact, he has to look for the type "contact". If I wish to add contact, I click with mouse, or do something like C-c p N - for new contact, and enter it. I am asked few questions, and it is entered. And same in Org, some information I like to enter by using templates. I did not like creating empty Org, because I had too many people to deal with. So when I create a person, I had single click to create the Org file with the name and personal information of that person, and tasks, and table for expenses, and final calculation of cash account. In Org we have to look for tags, properties, heading, those are all types. Using it as really plain text is possible, but not as beneficial. Types are useful in computing to sort information better. > I would like my system to detect by itself that when I give a > node/heading org-mode as title "A-name A-forname", it understands by > itself that it is a contact. For computer, without designation of a type, it will never get that type of intelligence. When I am entering new name of person, if I enter ">" before the name, that means that names is not individual name and computer asks me if it is company or list of people, or maybe government office, what it is. But it is not individual. User must somehow designate for computer that heading is "contact". > And if I put a phone number underneath, I can just ask him "give me > the phone number of X", and he gives it to me correctly. Good, that is how I think computers should be today. But they are not. > I repeat because I don't want to offend you: we don't have the same > goals, so it is normal that our methods are different. You strive same thing, and I don't understand you, so I can't tell anything so fast as you can. > On the other hand, I would very much like to test your method, it > intrigues and interests me a lot. Before anything, I have to understand what you wish to achieve. What is the purpose for which you devise methods? > > > Or we do something extremely flexible, exactly like a big > > > org-mode file where we just put the information, and the user > > > can use his method (grep for example). > > For single user that may be fine. For collaborative work, multi-user > > access is not, or sharing of information, it is not. That is why Org > > development strive to provide more and more structure, something I > > said, they try to make it like a database, but because there is no > > structure, it becomes the never ending story of milions of bugs. > > > I agree with you, although I don't know if the goal of the org-mode > developers is to do this. It is not, as it was made be user who was not thinking of collaboration, group or team work, sharing with the world. Org is designed to be very personal. Let us say for collaborative editing in Emacs, one could use `crdt' package together with Org mode, and multiple people can edit it over network. > > In my work I use meta level. First I am liberated from Org mode, or > > any kind of mode. And I like flexibility to mix various markups. I can > > use universal hyperlinks that convert themselves into necessary > > markup. I don't like being dependent on some "mode". > > > If markup is Org, hyperlink will become Org hyperlink, if markup is > > Markdown, hyperlink will become Markdown link, if it is text, it will > > be shown in text. Why do I need to record 3 versions of same document, > > better one, which can be just represented in different way. > > After that, it's the same for org-mode, it can export in a lot of formats, > so in the end you're just adding an extra layer of abstraction to export to > org-mode. No, I don't think that tying people to Org mode for sake of Org mode is good, rather using Org for what it is good. My purpose is not at all "Org mode" but that human can get educated easier or conduct tasks, or that we can finalize plans, programs and projects. One important task in management is handling cash accounts of people working for us. Imagine columns like Transaction ID, description, name of account money comes from, name of account money goes to, debit amount, credit amount, balance. It may fit, or may not fit in Org, I get some problems with it. So I used Asciidoctor to generate account statements. But then I think, I have to use Pango markup and `paps' command, or LaTeX directly, for reasons that I wish various fields be shown to user. Org cannot handle LaTeX tables directly well, so I can't use that markup. I can't see the information by using Org tables! Asciidoc works really well for that purpose. I am sure that direct LaTeX can do that without problems as well. So I will use any method that works and mix it in a mixed object Hyperdocument. dov/paps: A text to postscript converter through pango: https://github.com/dov/paps > Yes, today, no artificial intelligence will be able to replace your > application entirely. The problem is that we don't realise how advanced > these areas are. I'm in my third year of computer science, and chatGPT is > able to do my first two years of classes. I'm already at a loss, and I'm > not even in the job market, and I know it. Alright. I hope you are not using ChatGPT to make works that pretend to be your mind's work, as that could be plagiarism. In fact, I do not now if your writing is of human or ChatGPT... > The only thing I have is my reasoning, which I hope AI is not > capable of. You can't pretend that your system, or mine of course, > won't be revolutionised by the presence of a new AI capable of doing > almost everything you've planned, and perhaps without writing an > extra line of code on your part to add a new feature. And this is > frustrating, but that's the way it is. I wish it could integrate things. ChatGPT does not work by means of the real understanding. It works by reconstructing some information, and relating information to each other. Computer does not understand information, it just gives to human an illusion that it does. > I don't want to defend AI, I just maybe want to hold you accountable > to learn about these areas and the main advances so that you don't > do something obsolete as soon as it comes out, but rather use these > tools to improve your goal. I have no means to understand you, and to use tools which I do not have as free software. If it free software, do you hav example. -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/