In this section important changes to the LML's XML-Schema are
released in May 2013
The LML namespace is changed to http://eclipse.org/ptp/lml in accordance to the namespace used
within the Parallel Tools Platform (PTP).
released in January 2013
This version aims to split the two use-cases of an LML file: LML request and LML response.
LML can be used as communication protocol. A client sends LML requests, while a server
provides LML responses. An LML request contains merely a table of content listing all
graphical components, which are requested by the client. The server interprets the request
and returns a full LML file, which includes the orginal request as well as corresponding
This LML version adds the special layout root element for LML request files.
Thus, LML requests and LML responses can easily be distinguished. In addition, to
better separation between both use-cases of LML, this modification simplifies the
use of LML within the Parallel Tools Platform (PTP). The layout elements of LML can
become part of target system configuration files. This allows for configuring an
LML layout for each remote system, to which you connect via PTP.
All data, which is needed by LLview within an LML request, is now given by an LML layout file.
Therefore, the filtering information provided by the pattern element is shifted from the table element to the tablelayout.
Moreover, the nodedisplaylayout contains a schemehint element, which describes the
supercomputer's hierarchy. The schemehint is used as the actual scheme in the nodedisplay generated by lml_da.
The target namespace is now renamed into org.eclipse.ptp.lml as LML is also published within the PTP project.
Summary of changes
- Separation of LML request and response
- Special root-element for LML request files
- Move all request parameters into layout (pattern/schemehint)
released in April 2011
A request-tag at the beginning of the LML-file is added.
This tag allows to specify, if the current layout should be saved by the server.
The attribute getDefaultData can be used to request data for the first time.
Usually the client does not know anything about the monitored system at this moment.
This request tag indicates the beginning of the development to use LML as a data-request
language. Primarily LML is designed to sum up the current status of a parallel computer.
In order to allow to request user-specific data from the server, some elements like
the mentioned request-tag are added to the schema definition.
In this context the layout-attribute was added to the root-tag, which defines the current
document to be a layout-only LML-instance. A layout-only LML-file is used as data-request.
The layout-instance does not contain data, but empty data-stubs, which indicate that the
requesting instance is interested in the data for this element. Moreover, corresponding
layout-tags can be used to individualize the requests. For example a tablelayout-tag
could specify that the user only displays two of five existing columns. As a result
the server could just return the data for two columns instead for all. The request parts
in LML will be used to reduce data transfer and to support more individual communication
protocols between LML-requesting and LML-providing instances.
The last change in this version is that every component-layout (e.g. tablelayout, nodedisplaylayout,
chartlayout, ...) can use an active-attribute to define if the corresponding visible component
should be displayed. This can be used by the LML-provider to list additional components, which could
be displayed, if the user requires these components.
Summary of changes
- layout-attribute for root-tag
- active-attribute in component-layouts
- active-attribute in tablelayout-tag for columns
released in October 2010
This is the first published version of the XML-Schema for the LLview
Markup Language. In this version the following graphical components can
The layout-section is still in progress. The included components can be
evaluated as draft versions. The following overall layout-definitions
This version contains draft versions for special layout definitions for
each graphical component:
There are a lot of ideas for improvement:
- check layout-section
- are split- and absolute layouts enough for positioning
- check layout-definitions with real-life LML-examples
- add a table of content, which summarizes the content of the
Home | last change 20.08.2013 | copyright see
Copyright and Disclaimer | contact: email@example.com