|
Difference between
version 75
and
version 74:
| Line 53 was replaced by line 53 |
| - Some resources (in particular, data sets and actors with input/output ports) can have complex data structures. For example, a data set typically is structured according to a schema, which specifies among other things a relation name (that is, the name of the table) and names for each attribute of the relation. Actor ports can also have complex structure, including arbitrary nesting of relations. The annotation language facilitates the selection of the various objects of structured resources. |
| + Some resources (in particular, data sets and actors with input/output ports) can have complex data structures. For example, a data set typically is structured according to a schema, which specifies among other things a relation name (that is, the name of the table) and names for each attribute of the relation. Actor ports can also have complex structure, including arbitrarily nested relations. The annotation language facilitates the selection of the various (sub-) objects of structured resources. |
| At line 62 added 2 lines. |
| + We assume that a resource label denotes one or more corresponding objects. For example, if {{T}} is a label for a dataset, it implicitly denotes a set of tuple objects. Similarly, if {{T}} is a label for an actor, it implicitly denotes an instance of that actor |
| + |
Back to KRSMS Semantic Annotation Language,
or to the Page History.
|
