Lexville

Ok I thought a little about this, and of course the solution I proposed doesn't work, because per-day entries and by-name entries would conflict. So we have to put either one in a separate collection: Either the weblog entries in /log/, or the named stories in /space/, for instance.

my thoughts have been going in this direction and i've concluded i must redo some of my former knowledge on namespaces, just to be able to nicely add more features later on. I'am always thinking back to class dictionary. I would also like to add a semiautomatic id-resolution as a macro. Should this be checked at save-time?

Implementation starts from the ground up, but ideas need not, do they?

what do you mean by "checked at save-time"?

say, you use something like <blabla> to indicate that blabla references a snippet in the namespace, should the save procedure do anything? Or should the render procedure resolve the tag and value and if not resolvable do something like [create blabla] to invite the reader to create and write the snippet (vanilla)? this has more to do with production than anything else.

I always prefer to do these things at render-time. It's awkward to actually change the text input from an author, but it's ok to apply some rendering rules and tricks.

Regarding the actual tags, I'd propose to use Helma macro tags. For example, a link to a story could be created like

<% storylink name="simula" %>

or alternatively

<% storylink id="492" text="blablabla" %>

which would work across weblogs and also for "anonymous" weblog entries. It would be also possible to provide

<% storylink name="tiny.simula" %>

for cross-weblog references of named stories.

The default for the link text would be the story title, not it's URL-ID, so this is a bit different from Wiki-style systems where the two are identical. This is one reason why I don't think the [define xxx] would fit in very well. Although it can be very powerful to have title == URL-ID, it's in another way also limitating in what you can use as title of your entries.

I need to think a bit about this, maybe I'm just falling victim to stupid URL aesthetics.