I'm trying to apply Acceleo to an input model that uses a multi-package
input model.

The model complies with QVTRelation which 'extends' QVTBase which
'extends' ...

The [module ] declaration therefore specifies QVTRelation and allows the
QVTRelation types to be used, but there appears to be no way to use
QVTBase types in an expression: e.g.

[let domain : Domain ...
or
[let domain : qvtbase::Domain ...

Is there a workaround? this looks like the same specification bug that
QVTr had in failing to recognise that a TypedModel is a multi-package.
The QVTr spec therefore evolved to allow a {list,of,packages} in its
transformation declaration.

Perhaps the [module declaration should allow a comma-separated list of
package URIs.

Ed Willink wrote:
> Hi
>
> I'm trying to apply Acceleo to an input model that uses a multi-package
> input model.
>
> The model complies with QVTRelation which 'extends' QVTBase which
> 'extends' ...
>
> The [module ] declaration therefore specifies QVTRelation and allows the
> QVTRelation types to be used, but there appears to be no way to use
> QVTBase types in an expression: e.g.
>
> [let domain : Domain ...
> or
> [let domain : qvtbase::Domain ...
>
> Is there a workaround? this looks like the same specification bug that
> QVTr had in failing to recognise that a TypedModel is a multi-package.
> The QVTr spec therefore evolved to allow a {list,of,packages} in its
> transformation declaration.
>
> Perhaps the [module declaration should allow a comma-separated list of
> package URIs.
>
> Regards
>
> Ed Willink

Section 8.1 (Metamodel) of the MOFM2T 1.0 specification defines the
"input" reference as 1..*. Section 8.2 (Concrete Syntax) sports too many
issues as regards the metamodel and specification itself to be taken at
face value.

As for the Acceleo documentation, I agree that it does need something on
this.