(anonymous guest) (logged out)

Copyright (C) by the contributors. Some rights reserved, license BY-SA.

Sponsored by the Wiki Symposium and the Nuveon GmbH.

 

Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-6) was last changed on 23-Sep-2008 14:04 by spir  

This page was created on 20-Sep-2008 21:19 by JohnMcClure

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 1 added 3 lines
[{TableOfContents title="contents"}]
!!! implementation questions
At line 12 added 30 lines
----
----
Don't know about SGML profiles.
[[JohnMcClure]] said :
{{{
I'd balk at the overhead of merging that kind of information onto every page
}}}
Me too. What I propose here is /precisely/ that the pages are to be saved in a standard file format. Instead, or together with, having been edited in a standard /syntax/.\\
The customization is a user interface facility for viewing and editing source page. Whatever the custom syntax chosen by user, the page would eventually have the same meaning and content. For instance, in the case the file format would be an adhoc subset of xhtml to denote only format/style classes :
{{{I guess this is a **relevant** question.}}}
and
{{{I guess this is a '''relevant''' question.}}}
would both be stored as e.g.
{{{I guess this is a <span class="highlighted_segment">relevant</span> question.}}}
Am I clearer? A wiki who implants that feature needs a kinds of dictionary to translate between 2 or more wikitext variants. //Before// saving. If major syntactic variants are allowed, instead of simple tag changes then the process is, as you know, much more complicated. A kind of ennoying syntax alternative is for instance :
{{{[foo doc --> http://www.foo.org/doc]}}}
instead of
{{{[[http://www.foo.org/doc | foo doc]]}}}
But it's a very common parsing/encoding job, no ?
Browsing (eg for semantic lookup), migration, or any kind of manipulation tools would not be affected, on the contrary, they would have a single format to cope with instead of a hundred -- and no transformation at all for interwiki exchange. Once the job is done of implementing the format. Note that the principle is the same as html as a web page standard. Web designer also have hundreds of intzerfaces for editing the simple (background file save) format, including wysiwyg ones. Simply wikitext is much simpler. Where would we be if there hundreds of web page standard instead of a simgle html. Imagine the code of a simple referencing bot... ;-)
Note : Ad hoc xhtml subset is actually the kind of format chosen for [[http://semanticweb.org/wiki/WIF | WIF]] and its successor [[http://semanticweb.org/wiki/Structured_Text_Interchange_Format | STIF]]. Whose goals are not to allow syntax customization (still this possibility is evoked) but wiki (WIF) or any structured text (STIF) saving, exchange, manipulation,... Especially copying a page from a wiki to another.\\
"WIF is the lowest common denominator of wiki content exchange"\\
"Why STIF? To exchange structured text between different applications"
[[spir]]
Version Date Modified Size Author Changes ... Change note
6 23-Sep-2008 14:04 3.561 kB spir to previous
5 23-Sep-2008 11:43 3.569 kB spir to previous | to last
4 23-Sep-2008 11:42 3.577 kB spir to previous | to last
3 21-Sep-2008 16:47 3.491 kB spir to previous | to last
2 20-Sep-2008 22:12 0.922 kB JohnMcClure to previous | to last
1 20-Sep-2008 21:19 0.898 kB JohnMcClure to last
« This page (revision-6) was last changed on 23-Sep-2008 14:04 by spir