LML Schema Documentation

Table of Contents

top

Schema Document Properties

Target Namespace http://eclipse.org/ptp/lml
Element and Attribute Namespaces
  • Global element and attribute declarations belong to this schema's target namespace.
  • By default, local element declarations have no namespace.
  • By default, local attribute declarations have no namespace.

Declared Namespaces

Prefix Namespace
Default namespace http://www.w3.org/2001/XMLSchema
xml http://www.w3.org/XML/1998/namespace
lml http://eclipse.org/ptp/lml
Schema Component Representation
<schema targetNamespace="http://eclipse.org/ptp/lml">
...
</schema>
top

Global Definitions

Complex Type: CommandType

Super-types: None
Sub-types: None
Name CommandType
Abstract no
Documentation Every command consists of a name and a path to this command.
XML Instance Representation
<...
name="string [1] ?"
exec="string [1] ?"/>
Schema Component Representation
<complexType name="CommandType">
<attribute name="name" type=" string " use="required"/>
<attribute name="exec" type=" string " use="required"/>
</complexType>
top

Complex Type: DriverType

Super-types: None
Sub-types: None
Name DriverType
Abstract no
Documentation Definition of driver-parameters for calling the lml-da with specific driver-information.
XML Instance Representation
<...
name="string [1] ?">
<command> lml:CommandType </command> [0..*]
</...>
Schema Component Representation
<complexType name="DriverType">
<sequence>
<element name="command" type=" lml:CommandType " minOccurs="0" maxOccurs="unbounded"/>
</sequence>
<attribute name="name" type=" string " use="required"/>
</complexType>
top

Complex Type: LayoutRequestType

Super-types: None
Sub-types: None
Name LayoutRequestType
Abstract no
Documentation Contains information about handling layouts on the server side. For example an LML-client could wish to save the layout on the server-side. These parameters are listed within this tag.
XML Instance Representation
<...
saveLayout="boolean [0..1] ?"
getDefaultData="boolean [0..1] ?"/>
Schema Component Representation
<complexType name="LayoutRequestType">
<attribute name="saveLayout" type=" boolean " default="false"/>
<attribute name="getDefaultData" type=" boolean " default="false"/>
</complexType>
top

Complex Type: RequestType

Super-types: None
Sub-types: None
Name RequestType
Abstract no
Documentation A type for collecting request information. LML can be used as communication language. The client sends layout information and empty data-tags to the server. The server returns the corresponding data.
XML Instance Representation
<...>
<driver> lml:DriverType </driver> [0..*]
<layoutManagement> lml:LayoutRequestType </layoutManagement> [0..1]
</...>
Schema Component Representation
<complexType name="RequestType">
<sequence>
<element name="driver" type=" lml:DriverType " minOccurs="0" maxOccurs="unbounded"/>
<element name="layoutManagement" type=" lml:LayoutRequestType " minOccurs="0" maxOccurs="1"/>
</sequence>
</complexType>
top

Simple Type: content_type

Super-types: string < content_type (by restriction)
Sub-types: None
Name content_type
Content
  • Base XSD Type: string
  • value comes from list: {'jobs'|'nodes'|'users'|'groups'|'classes'|'queues'|'other'}
Documentation Type describing the type of content of a table.
Schema Component Representation
<simpleType name="content_type">
<restriction base=" string ">
<enumeration value="jobs"/>
<enumeration value="nodes"/>
<enumeration value="users"/>
<enumeration value="groups"/>
<enumeration value="classes"/>
<enumeration value="queues"/>
<enumeration value="other"/>
</restriction>
</simpleType>
top

Generated by xs3p (old link) . Last modified: