Search: concept

For instance, all organizations and persons who received the Nobel Peace Prize can be browsed by country. ))) (% class="col-md-4" %) ((( [[[[image:person.jpg||style="border:1px solid silver; max-width:100%;"]]>>attach:person.jpg]] (% class="text-center" %) ((( //Facet filtering on page "Person"// ))) ))) ))) == Data model == (% class="row" %) ((( (% class="col-md-8" %) ((( |=Concept|=Definition |Term|A Term simply wraps a wiki page.

* **Query scripts:** scripts that will generate a list of documents that should be gardened based on a given concept. For example, a script fetching every document updated in the past X minutes

= See also = This paragraph lists some initiatives that relate to the management of relations or software that implements a feature allowing to relate artefacts with one another: * RDF proposes the concept of triples: subject - predicate - object, that's a way to relate the subject and the object

description : {{warning}}This is currently a proof of concept and not yet ready for production.{{/warning}} Inspiration: https://github.com/phillip-kruger/graphql-example It follows the [[Eclipse MicroProfile GraphQL API Specifications>>https://github.com/eclipse/microprofile-graphql/]] using the [[SmallRye GraphQL Implementation>>https://github.com/smallrye/smallrye-graphql]].

description : = Users {{info}}Since 12.2{{/info}} Concepts: * This API is independent from where the users are stored (in wiki pages, etc).

{{image reference="EM-extensionDescription.png"/}} == Supporters and Support Plans {{version since="16.8.0"}} XWiki extensions now have the concept of supporters and support plans. The goal is to replace the very vague concept of **Recommended** we currently have for a very explicit pledge of organizations and individuals (**Supporters**) to support an extension, and to which extent (**Support Plans**).

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 referencing footnotes is in the planning for XWiki too.

Note that this event is an Event that predates the wiki provisioning concept and it's not sent when provisioning |##WikiDeletedEvent##|wiki id (String)|##XWikiContext## object|Sent after a wiki has been deleted |##WikiProvisioningEvent|wiki id (String)|##XWikiContext## object|Sent before a wiki has been provisioned (i.e. before the content of the wiki has been filled), during the wiki creation process |##WikiProvisionedEvent##|wiki id (String)|##XWikiContext## object|Sent after a wiki has been provisioned (i.e. after the content of the wiki has been filled), during the wiki creation process ))) * Other types of events:((( |=Event Name|=Source|=Data|=Description |##ApplicationReadyEvent##|##XWiki## object|##XWikiContext## object|Sent when the XWiki application is ready to service requests.

See the [[Model module>>Model Module]] to understand the concept of references. |##type##|yes|document|document|The type of the entity.

description : {{info}} You can also check the [[XWiki Platform Developer's Guide>>xwiki:Documentation.DevGuide.Scripting||anchor="HVelocitySpecificInformation"]] for information about Velocity scripting in the XWiki Platform {{/info}} This module offers APIs to evaluate content with Velocity. The following concepts are exposed: * ##VelocityManager##: This is the main entry point for anyone who need to manipulate Velocity scripts * ##VelocityTemplate##: {{version since="15.8"}}This is a helper to manipulate/cache/reuse a "compiled" version of a Velocity script{{/version}} * ##VelocityEngine##: This is the object on which you call ##evaluate()##.