Category: Semantic links (3.0)

Contributors

Using Tiki 7.2, we encounter the following issue with module semantic_links:

We've defined the abbrev. »wp« for links to Wikipedia articles, such that ~np~((wp:Jon_Doe|Jon Doe))~/np~ expands to a link to http://en.wikipedia.org/wiki/Jon_Doe .

We've also defined a semantic link type »wp« to mark links to Wikipedia articles, and want to use the notation
* ~np~(wp(wp:Jon_Doe|Jon Doe))~/np~

This works well for the actual wiki page, and the abbreviation is properly expanded into a link to the WP article.

However, in the module semantic_links, the link text is displayed as
* »wp:Jon_Doe«
and the URL of the link is
* »oursite.com/wp:Jon_Doe«.

Can this be fixed such that the module uses the same link text as the
respective wiki page?

(The Wikipedia link type is only an example, but note that it's reasonable for a wiki page to have several links to Wikipedia articles using the wp: abbrev., but still only one of those of type wp(, thereby indicating that the external Wikipedia article and the local wiki page are about the same subject.)

On the Tiki-devel mailing list (Oct 2nd 2011), Nelson Ko mentioned that

»I think there is a ›hackish‹ way to get this to happen.

In templates/modules/mod-semantic_links.tpl, you will see where the
link is generated:

~np~<a href="{$msl_url|escape}">{$msl_item|escape}</a>~/np~

Replace this with:

~np~{wiki}(({$msl_url})){/wiki}~/np~

I didn't test it but it should work if you have sefurl on, since with
sefurl on the value of msl_url should be simply wp:Jon_Doe«,

but the hackish way didn't hack. =;-)

So the alias is not 100% an alias.

On: ((doc:Semantic))

There is a link to:
* ((doc:Semantic Alias))

But this ((doc:Semantic Alias)) is an alias of ((doc:Alias))

Also in action here:
http://profiles.tikiwiki.org/handler

Related:
*{wish id=2754}
*{wish id=2729}

This would permit cleaner URLs and easier searching.

__Where?__

Wiki page names
Usernames
tags?
etc.

__What?__
Spaces & underscore to be equivalents
a and A are equivalent. This makes perfect sense for page names, user names, etc Accented characters (äâ) should be as well

For wiki page names (see how Wikipedia does it) but it could be that ~np~((User_Profile)), ((User+Profile)) and ((User Profile))~/np~ are equivalent.


Should hyphen (-) be an equivalent character as well?

How about (,) and (.)

. doesn't play nice with rewrite rules




Moved discussion to: ((Character substitutions))

feature alias (semantic links) is not SEF (search engine friendly) ready

Using 4.2.
See it here:
page:
http://gavarrespedia.org/pendent

has a few aliases such as:
{CODE()}
(alias(pendents))
{CODE}

If you have SEF feature off (btw, and htaccess rewrite rules on), when you type:
http://gavarrespedia.org/pendents

you get
http://gavarrespedia.org/pendent

However, if you enable SEF feature (to make tiki create also short urls), then:
http://gavarrespedia.org/pendents

shows error, page not found, maybe you were looking for pendent, etc.
and it should just show the page "pendent" straight away

As discovered here:


http://doc.tikiwiki.org/tiki-pagehistory.php?page=PluginInclude&diff_style=sidediff&compare=Compare&newver=0&oldver=26&tra_lang=ar

The ultimate feature of Amazon and all the e-commerce shopcart systems is the one known as "Customers who bought this item also bought .." or "were also interessted in ..".
The feature would show objects or items that were viewed or bought by previous users in conjunction with the actual item or object.

Idea:
Applied for tiki a new plugin "Relation By Views" would allow to list related wiki pages (or even other objects) in a page likewise to existing backlinks and alias plugins as well as semantic links.
Though, the information is based on previous view counts / his of wiki pages (or other objects) that have been hit by users wihtin the same session as the actual wiki page / object.

The enhancement is obvious: we would make a step further to get implicit relations between pages / objects based on user behaviour.
Just as the advantage in ecommerce is crossselling, we would provide cross-links and encourage readers to have a look to further pages / objects.
In regard to enhancements of the basic shopping cart feature in Tiki 5, this plugin could even be used as a real "customers were also interessted in" feature.

You can see here: ((WantedPages))

Some wanted pages have links to the alias.

Semantic link "alias" broken on 4.1 for me (regression)
See:
http://gavarrespedia.org/tiki-index.php?page=Pendents

it shows an error page, suggesting similar page, search box, and the option to create the page (as reg. user)

However, the page name "Pendents" is defined as an alias of "pendent", as it can be seen here:
http://gavarrespedia.org/tiki-index.php?page=pendent

which has underneath (inside the "[[+] Fet" box):
{CODE()}
(alias(pendents)) | (alias(Pendents))
{CODE}

So this looks broken to me (at least, with common settings as I have).

---
Reproduced in doc.t.o with http://doc.tiki.org/PluginRR (which has an alias link from http://doc.tiki.org/PluginR )
Discussed (with more details) on irc:
[http://irc.tiki.org/irclogger_log/tikiwiki?date=2011-02-09,Wed&sel=267#l263]

---
UPDATED: Fixed in current branches, at least (9.x, 11.x, 12.x)

Semantic link relationships seem until now only browsable by admins.
Since there is - besides the admin view - no other way to get the semantic relations listed, no one else can get advantage of semantic links and will make no efforts in setting semantic relations.
Concidering the importance of semantics in wikis a plugin seems highly necessary to get the feature of semantic links in tiki started.

__Request:__
Likewise to the Plugin ((Backlinks)) all pages that link to a specific page in a specific semantic relationship.

__So far:__
The semantic_links module is supposed to enable views on semantic relationships.
And indeed, when selecting a semantic type and push the button "show usage", the result shown is exactly what I need.
However this view is only possible for admins.
But since that view for admins is already existing, I would estimate the efforts to implement a plugin as low.

__Plugin idea:__
Relating to the example shown in the documentation of ((SemanticAdmin)) dogs and cats are subsets of animals.
We want the page "animals" to list all subsets by a plugin likewise to

{SEMANTICLINKS (semantictype=subset, page=animals, info=hits|user, noheader=1}
{SEMANTICLINKS}

The result would be:
- dogs
- cats


__Insufficient workarounds:__
Until now the above shown results have to be specified manually as invert relations.
For automatic listing, existing plugins ((PluginShowpages)) / ((PluginListpages)) / ((PluginSearchtitles)) do not work.
So the only workaround without the requested plugin I could image would be to tag the pages "dogs" and "cats" with the a tag "subset-animal" and than use freetags plugin for a listing dogs and cats in the animal wikipage - likewise to the status tags in this tiki. However, that sounds like a bad abuse of tags, since we already got that information saved in our semantic links relationship - we just need to get it readable.

__Related pages:__
Relating to forum discussion with marclaporte:
[http://tiki.org/tiki-view_forum_thread.php?topics_offset=20&topics_sort_mode=lastPost_desc&forumId=4&comments_parentId=38751]

Aliases of the same page are not very interesting, because it's link to self.

But antonyms, related, etc would be nice.

Well explained here:
http://twiki.org/cgi-bin/view/Plugins/ActionTrackerPlugin

We'd output in htask microformat
http://microformats.org/wiki/htask

And we'd need some sort of reporting. All tasks assigned to person X.

We currently usually do this with ((doc:trackers)). But doing it fully in the wiki would be more flexible in some contexts.

The system should be able to send email reminders at a certain date. This could be used as well to schedule actions / Email reminders as explained here:
http://www.youtube.com/watch?v=8XwyhSEqTs0

This is part of what is needed for ((Project management))

It would be fantastic to get even more structure and relations between wiki-items. The most innovative way at this point is to work with ontologies. Therefore it would be helpful to base a tikiwiki on an ontology.

Contributors