the JDM Schema follows JAX-RPC Java-XML data type mapping
guidelines [JAXRPC-SPEC 2006]. For example, Figure 10-1 depicts the
class diagram and schema diagram for the PhysicalDataSet related
objects illustrating the similarity between the API and the schema. In
the class diagram, the PhysicalDataSet interface inherits from the Mining-
Object interface, similarly in the schema diagram, the PhysicalDataSet-
complex type inherits from the MiningObject complex type. In the class
diagram, PhysicalDataSet has a one-to-many relationship with Physical-
Attribute and it may have an AttributeStatisticsSet that gives statistics
details of the data. Similarly, the schema diagram shows that the Physi-
calDataSet complex type can have a one-to-many relationship with the
PhysicalAttribute type elements and it may have an AttributeStatisticsSet
element. Maintaining these similarities between the JDM API and
XML Schema simplifies the implementation of the marshalling and
unmarshalling of Java objects to and from XML, and the developer
who understands the API can easily understand the schema.
The rest of this section explores some of the complex types
defined in the JDM Schema to illustrate how various JDM API
objects discussed in previous chapters are mapped to the schema.
The task objects discussed in Section 8.1.5 have more flexible options
in the JDM Schema than the API to reduce the number of server invoca-
tions to perform a mining operation. Consider the following example.
The BuildTask is used to build a mining model using input such as the
build data and build settings. The javax.datamining.task.BuildTask API
(a) Java API Class Diagram for
PhysicalDataSet related interfaces
(b) JDM Schema Diagram for PhysicalDataSet complex type
JDM API and Schema mappings for PhysicalDataSet- related objects.