Re: [gmt-dev] evolving GMT in a fully open process that allowsothers to

[Markus Völter <schogglad@xxxxxx>]

> This means there's *exactly* one place where I specify
> "attribute of type date in model" => "timestamp in unix"
> and *exactly* one place  where I specify
> "attribute of type date in model"=> "INT in database" etc.

yes, of course...

> I.e. in my domain-specific model I only specify
> "attribute name: blah, attribute type: date", without polluting it with
> "timestamp" and "INT".

I see the aspects going even step further:
selectively adding these kinds of mappings.

> Alternative: Without good support for aspects you can still achieve the
same
> effect with an architecture-centric extension of the meta model where
> "attribute type" is an explict model element that contains a mapping to a
> unix type, SQL type and any further required information. However, your
> generated modelling tool will then allow "Joe Programmer" to come along
and
> define new attribute types that compromise your standardised
architecture -
> which in turn you can prevent by adding role-based access control to the
> generated modelling tool(s) ;-)

aaargh :-)

M.


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Markus Völter
mailto:voelter@xxxxxxx

voelter - ingenieurbüro für softwaretechnologie
Ziegelaecker 11, 89520 Heidenheim, Germany
Tel. +49 (0) 73 21 / 97 33 44

http://www.voelter.de
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -