From mboxrd@z Thu Jan  1 00:00:00 1970
From: "sindikat" <sindikat@mail36.net>
Subject: Re: [Orgmode] Feature request: IDs on anything
Date: Mon, 28 Nov 2011 00:09:51 +0100
Message-ID: <20111127230951.35547.qmail@rage.so36.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([140.186.70.92]:38940)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <sindikat@mail36.net>) id 1RUnr9-0004d8-VM
	for emacs-orgmode@gnu.org; Sun, 27 Nov 2011 18:09:56 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <sindikat@mail36.net>) id 1RUnr9-0001C9-0C
	for emacs-orgmode@gnu.org; Sun, 27 Nov 2011 18:09:55 -0500
Received: from rage.so36.net ([83.223.73.105]:61265)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <sindikat@mail36.net>) id 1RUnr8-0001Bm-K0
	for emacs-orgmode@gnu.org; Sun, 27 Nov 2011 18:09:54 -0500
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: emacs-orgmode@gnu.org

I really love this idea of ID markers. It would open so many opportunities 
for semantic extensions of org-mode and not only. Using ID markers we can 
make a associative array (map, dict, key-value store) out of anything. 
Meaningful task planning, project management, knowledge and information 
management could be made out of that. Every ID marker will effectively 
become a graph vertice. 

As a variant, i would propose the Clojure syntax for maps: 

{"B7423F4D-2E8A-471B-8810-C40F074717E9" {:label "foo" :export-label "bar"}} 

Or something like that. The nested maps are like in NoSQL DBs (ex: 
CouchDB), where you have structure like {:database1 {:document1 {:key1 
value1 :key2 { ... } ... } ... } ... } 

However i found that curly braces are used in many occasions in org-mode: 
tags mutual exclusion, column attribute summary-type, capture templates - 
template expansion, tag regular expressions, #+caption: [1]{2}, macro 
replacement, embedded latex, source code. 

So if this syntax is unacceptable, $[] is fine too.