2 Differences between Paper and Implementation
Fragment Class
The paper discusses the creation of fragment classes which can introduce
several parameters. This prototype restricts the number of parameters
which can be introduced in one step to one. For example: creating the
fragment class wines<region,rcateg> from
root fragment class wines<> requires the
fragment class wines<region> or wines<rcateg>
to be created first. Directly creating afragment class which introduces
more parameters at one time is not possible.
Derived fragment classes inherit parameters from the derivation base
class. The prototype restricts the derivation base class be parameterized
by exactly one parameter. The fragment base class can be un-parameterized
(as root fragment class) or parameterized by one or more parameters.
The paper describes the ability to rename fragment classes. The creation
of the fragment class PremWineries<region>
defined upon fragment class Wineries<>
was used as example in the paper. The ability of renaming fragment classes
is not provided by this prototype.
Page Class
The schema definition language of the underlying paper discusses the usage
of page references. This page references (internal and external) which
are defined upon page classes would enable pages to link to pages within
the same page class (internal), or to pages of other page classes (external).
The prototype stores the meta-data needed for the generation of page references,
but the usage of page references itself are not implemented yet.
|