="ctag:label" content="$detail.getLabel()"><a class="tag-concept-link" href='$detail.getUri()'>$detail.getLabel

.tag-delete').each(this.ajaxTagDelete); // [semtag] concept list for each tag $$('.doc-tags .tag-list-activator').each(this.ajaxTagConcepts); // [semtag] end concept list for each tag

XWiki platform which does not link the user-defined tags to a concept. A semantic tag will preserve the

a.selected-tag:visited { color: #ccc; } .tag-concept-link { padding: 0.5em 2em 0.5em 0; background: url

be considered as a "proof of concept". Due to some design decisions (mainly due to "write on read" for Views

notes : This is initial Proof of Concept.

. The best way to grasp the concept is to see how it works on the [[References Page

as a dependency. {{/info}} = Concepts = Similar to the [[authorization API>>Extension.Security Module

of the existing XWiki concepts, there is no new implementation of the rights or of their storage. It is fully

), the access rights do endup stored as XWikiRights or XWikiGlobalRights objects, but those concepts

Server.WebHome]] * [[Extension.Discussions REST.WebHome]] = Concepts = == Discussion Context

the different elements, and to dynamically chose the storage location. To do so, two concepts have been put

adopted the "nested pages" paradigm. It means that you will no longer find the "space" concept in the UI

that should be gardened based on a given concept. For example, a script fetching every document updated

precisely, through the concepts of UI Extension Points/UI Extension, it allows Skins (and any Extensions

comment : I second Joris Dirks' comment about multiple references on a page to one single footnote. A method for doing that in Tex is described here: http://tex.stackexchange.com/questions/35043/reference-different-places-to-the-same-footnote. I hope a similar concept of (optionally) labelling and then