In a wiki, it makes sense for each WebLogEntry? to have a WikiName. This gives rise to an interesting design question -- to put those names in the same namespace as the rest of the wiki, or in a separate namespace for each WebLog?
The choice on PikiePikie has been for each WebLog to have its own namespace (and in fact to allow for duplicate names). I would love to know if this is a choice you spent some time with Steve, and if so what you came up with as the advantages and disadvantages of doing it either way. --JohnAbbe
Thanks for your response. I see how the last three make things easier for the programmer -- which has the distinct advantage that we have a WikiLog to play with now (danke, Steve).
I question that "the user should not have to deal with issues such as thinking up unique WebLogEntry? names" though. This issue comes up in naming WikiPages and is seen as a feature: i go to create a page with a name that i think is descriptive, and discover that the page already exists. Now i learn from the existing document/thread, and am able to contribute on the shoulders of others. Wouldn't it be interesting to see how this wiki feature contributes to weblogs? The old entry is 'revived' in the weblog even if it is unchanged (and if it is changed, in RecentChanges as well). The cost of having to come up with a new name when the content does not relate is a price i'd be willing to pay to see where this leads. Btw, i assumed it would be this way, but maybe that just proves that i'm illogical... --JohnAbbe
It's not so much a problem as standing in the way of certain kinds of exploration. Here's one vision of what could be done if we have EntryNamesInWikiNameSpace?:
Joe, Shena, Carlos and Mel each write weblogs in the same wiki as a way to communicate and provide documentation with their customers.
Shena, not seeing Joe's entry, posts something similar with a different title, and a pointer to a more complete analysis.
Carlos reads Joe and Shena's weblogs before posting that day. He decides the MacOsxUpdateIncludesXmlRpc? title works better, but refactors the content, adding Shena's pointer, a bit about what it means for their project's AppleScript? support, and pointers to relevant pages in their wiki, including one on which they and customers are hotly discussing the spread of XmlRpc and SoAp?. He also changes Shena's weblog to point to the new title (they trust each other to do stuff like that). Finally, he adds the entry to his own weblog.
Users are free to edit, or add discussion to the entry itself, like any other WikiPage. If it gets long, it trims itself off at the bottom and offers a "Read more..." button to get the whole page.
When OS X 10.1 is released, the page appears on everyone's weblogs again, and much of the relevant wisdom, information and references is already there.
So now there are four pages, and it's not clear who's responsible for making sure that the canonical one remains canonical. I'm realizing, given our discussion on Pikie:IncludePage, that my ideal solution would let my WebLog mix and match entries that are regular wiki pages, and (possibly nameless) entries that are connected to their page. For now i'll settle to get WikiPagesAsWeblogEntries? (basically InternalTransclusions). --JohnAbbe
_Why_ does it make sense for each blog entry to have a WikiName? I considered this, but became concerned that the names would become pointlessly long, and I've rarely want to refer to one after posting it, and even more rarely would expect to do so "naturally" via WikiName. So I'm planning on a model that uses some simple date-id for blog entries. Then a RecentChanges page can recognize items that follow the blog naming convention, and render them differently from true Wiki pages. (Why use Wiki at all for blogging then? Because I want (a) to easily go the other direction, having a blog entry use a WikiName to lead off to an ongoing idea, and (b) I want to have an integrated RecentChanges view.) --BillSeitz
You may want to see the DrupalEngine which has a blog-like structure on one side, and a wiki-like structure on the other. It might be easier to take one really good blog implementation and another really good wiki-implementation and merely modify the two so they can easily make links between each other.
I'm just starting on writing up a WikiLog extension to UseMod wiki. As above, I've decided to lump all blog entries under an owning page name as sub pages. I really don't want to have to think up good wiki names for my blog entries because I want to capture things of passing interest and do so quickly. I also want to do this via a simple popup form (a la Blogger), which means I won't even get to see if the wikiname I make up already exists (or should but I typoed) or even if it is actually valid as a wiki name. I will however include a subject field - I just won't be treating it as some unique identifier.
Thus, blog entries will be uniquely identified by some automatic meta-data. To keep things simple I decided on a sequential serial number rather than some munged datestamp. Dates will nonetheless be captured and stored with the blog entry, and can also be used to generate the chronological transclusion globs.
This is the namespace schema I've decided on (rather ambitiously):
All rather ambitious, but I think it has logical consistency.
OddMuse has transclusion, and therefore also internal transclusion, but it is cumbersome to use, I think: Create a tiny new page, write two sentences, edit the front page, add a transclusion tag. For a better solution, see WikiLog, section "Permanent URLs". -- AlexSchroeder
See ArchivingNews for a previous discussion of this idea.
This originally came up at [PikiePikie:WebLog].
Also see WikiLog, about real and possible combinations of wiki and weblog.