Module infobox fields

This article explains the meaning of the fields in the built-in modules infobox.

Jar files

The "Jar file" field in the infobox declare the list of jar files used by the module:

• In the majority of the cases there is nly one Jar file for the module. For example the Meteo module only has one Jar file
• In some cases there is one support Jar file which can be used by a client of the module. For example the Jena module has one Jar file which contains the effective module, and one support Jar file which can be used by module which interact with it. Note that in this case you must take caution to share the associated support jar file between different modules. See sharing libraries between applications for more information

Modules

The "Module" field in the infobox is the name of the autodescripted module declared by the built-in module Jar file.

Namespace

The "Namespace" field in the infobox declares the namespace used by the built-in module for its provided or required services. Note that:

• Some modules may not use any namespace at all. This is the case for example for the Logger application
• Some module may not use the namespace for all of their services. This is the case for example for the Jena module

Infobox declared services

The "Provided services" and "Required services" fields in the infobox declare:

• "Provided services": The services invoked by the module
• "Required services": The services for which the module is invoked by the module

Each service in the list of provided services or required services can have two patterns:

• <service name>: represents a service with no namespace
• <namespace><service name>: represents a service with a namespace

Examples

owlRequest represents the following service:

• With no namespace
• With the name owlRequest

http://dassault-aviation.com/jena:owlObjectRequest represents the following service:

• With the namespace uri http://dassault-aviation.com/jena
• With the name owlObjectRequest

Example

We have the following infobox for the Clock Application:

• The module is distributed in the clock-bin.zip file
• The Jar file containing the module is clock.jar
• The name of the module is clock
• The namespace used for the module services is http://dassault-aviation.com/clock
• The module uses the two http://dassault-aviation.com/clock:clock and http://dassault-aviation.com/clock:tag services, both provided and subscribed
• The module has the three optional properties period, xPos, and yPos