It is nice to have the visual tour, but for a faster browsing some simple but useful links could optionally defined in the head of each page. These would define simple relations to other wiki definition, the same way we used to use in our UML diagrams for example:
As I mentioned, they would make browsing the Wiki pages in a more intuitive way, it would generate some order? At the end, based on these relations, different maps could be created based on a certain relationship.
Please tell your opinion. I do not want to be a revolutionizer, just want to bring my contribution.
-- MihalyElekes?
Mihaly, The idea of relational tags sounds nice, can you provide some specific/worked examples to help illustrate your idea some more?
I provided some example above, but I will show something concrete with dummy pages. I hope it will nobody disturb. -- Mihaly
This is an interesting idea, Mihaly. You seem to be implementing predicate calculus in wiki form. -- EarleMartin
Earle: agree with you that Mihaly's idea idea of more formal tags/badges to map associations/relationships is intriguing. Can you explain "predicate calculus" in terms a database newbie can relate to? Tks! -- anon
Mihaly: were you thinking of mapping for content in general, e.g. any wiki on any subject, or for a specific project, e.g. project documentation etc. -- anon
Maybe some day we could extend the wiki server with a magical plug-in, that could generate UML like diagrams in form of bitmap based on the defined relationships.
Interesting concept, could someone construct such a map? One which exists without making changes to the surface of the objects being mapped. That is no edits or tags inserted on the pages being mapped. In the case of a changing landscape, as a wiki is a perfect example, such mapping must be performed every time a change occurs. Would anyone have the knowledge to build a Server (wiki engine) which would include such mapping and the interface to employ it.
I really did not think too much about this topic, but a superficial approach would be:
YetAnotherWikiName currently uses SubOf: ParentPage to define a hierarchical structure of wiki pages. You're welcome to mess around with it! -- DA
Moved from DummyCreationalPattern:
DummyCreationalPattern? SpecializesThe? DesignPattern.
It is/(could be) used to generate WikiMap for more intuitive browsing and understanding of the content of wiki.
This is just to demonstrate my idea how WikiMap could work.
Please feel free to delete these pages if the idea is that bad. -- MihalyElekes?
Moved from SpecializesThe:
It is/(could be) used to generate WikiMap for more intuitive browsing and understanding of the content of wiki.
This is just to demonstrate my idea how WikiMap could work.
Please feel free to delete these pages if the idea is that bad.
-- MihalyElekes?
The idea may not be bad, but it isn't used here. See also GentlyReduceWikiBadges. I think this WalledGarden should be deleted, it is referenced/consists only of DummyCreationalPattern?, IsUsedBy?, MihalyElekes?, PagesToCategorizeSs?, SpecializesThe?, VisualizeTheWiki and WikiMap.
See NotUsedHere
Moved from IsUsedBy:
IsUsedBy? SpecializesThe? the AbstractRelationship?
see DummyCreationalPattern? for example.
It is/(could be) used to generate WikiMap for more intuitive browsing and understanding of the content of wiki.
This is just to demonstrate my idea how WikiMap could work.
Please feel free to delete these pages if the idea is that bad. -- MihalyElekes?
Maybe some day we could extend the wiki server with a magical plug-in, that could generate UML like diagrams in form of bitmap based on the defined relationships. -- Mihaly Elekes
Moved from AbstractRelationship:
An Abstract Relationship is any possible relationship between two entities.
Why is that an abstract relationship and not a relationship? What is abstract about it?
................. to be continued
Please feel free to delete these pages if the idea is that bad.
-- MihalyElekes?