[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Structuring the discussion points
Dear all,
let us start the discussion on this mailing list.
As you know from Ekkart's posting, a result of the discussion on
PetriNets 2000 in Aarhus was to declare several levels of the
interchange format in order to make progress with a rapid *and*
convergent development.
Let us fix the levels with features which are supported by the
interchange format of the corresponding level. The following list
of levels and features follows the discussion in Aarhus supplied
by a few issues. Feel free to resort and to complete the list.
I distinguish
net objects (net, places, transitions, and arcs)
and
labels related to objects
(e.g. markings to places,
guards to transitions
declaration to net
...)
Level 0:
* Layout, graphical information
(we should prepare a list of minimal requirements,
according to both net objects and labels)
* meaning of different arcs
(normal, inhibitor, read, ... (which else))
* multi-set notation
(BTERMS in the standard ISO 15909)
* labels as pure text
(the developers are free to substructure the labels,
but a pure text of a label is required, too)
* structuring concept
(which?)
* types of net objects
(see the different arcs above;
maybe there are types for transitions and places,
e.g. external transitions in Reisig (1998))
* user defined classes of net objects
(in order to separate them in special style sheets,
e.g. to distinguish transitions of a client from
transitions of the server)
Level 1:
* more syntax for labels
* fixed semantics for tokens, etc.
* more graphic features
* properties of nets
Level 2:
* transformation between different high-level formalisms
well.
Kind regards
Micha
--
Michael Weber 4.4.15 | Institut fuer Informatik
mweber@informatik.hu-berlin.de | Humboldt-Universitaet
Tel. +49-30/2093-3075, -3066 | Unter den Linden 6
http://www2.informatik.hu-berlin.de/~mweber | D-10099 Berlin