From fcdf829cb16c4c1cfe2d3e10f44e1f28f2e7881c Mon Sep 17 00:00:00 2001 From: Jonathan Bernard Date: Mon, 30 Jan 2012 14:00:01 -0600 Subject: [PATCH] Updated issues. --- doc/issues/0011fn5.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/issues/0011fn5.rst diff --git a/doc/issues/0011fn5.rst b/doc/issues/0011fn5.rst new file mode 100644 index 0000000..16a4753 --- /dev/null +++ b/doc/issues/0011fn5.rst @@ -0,0 +1,16 @@ +Abstract `jlp:` link resolution. +================================ + +I need to think of a system to allow the resolution of `jlp:` protocol links +to be easily configured. Currently the link resolution assumes straigtforward +file-based storage and converts them into relative paths. An example of another +type of resolution strategy might be a DB-backed solution where each document +has a unique id (this is already happening temporarily in the JLP process) and +there is some schema for mapping document id's to URIs for the document. Or +perhaps another file-based solution with different convention for document storage. + +---- + +======== =================== +Created: 2012-01-30T13:55:05 +======== ===================