| Line 78 was replaced by line 78 |
| - The atom {{T}} selects corresponding objects of the resource. For example, if the resource is a data set, {{T}} selects the tuple objects of the resource. If the resource is an actor, {{T}} selects instances of the actor. The expression {{T.A1}} selects the nested {{A1}} objects for objects of {{T}}. For {{T}} representing a data set, {{T.A1}} selects the values of attribute {{A1}} for tuples of {{T}}. The last atom selects nested attributes for complex structures occuring, for example, in actor input/output ports. For instance, if {{T}} represents an input port to some actor[2], {{T.A1.A2}} selects the {{A2}} objects nested within {{A1}} objects for {{T}} objects. |
| + The atom {{T}} selects corresponding objects of the resource. For example, if the resource is a data set, {{T}} selects the tuple objects of the resource. If the resource is an actor, {{T}} selects instances of the actor. The expression {{T.A1}} selects the nested {{A1}} objects for objects of {{T}}. For {{T}} representing a data set, {{T.A1}} selects the values of attribute {{A1}} for tuples of {{T}}. The last atom selects nested attributes for complex structures occuring, for example, in actor input/output ports. For instance, if {{T}} represents an input port to some actor[1], {{T.A1.A2}} selects the {{A2}} objects nested within {{A1}} objects for {{T}} objects. |
| Line 109 was replaced by line 109 |
| - For convenience, we permit ontology concept expressions to be included in a sematnic type. The purpose of this features is to allow one to specialize certain concepts to more accurately annotate objects, without having to go through the process of creating a new ontology, or editing an existing one. These concept definitions are expressed using OWL[1]. |
| + For convenience, we permit ontology concept expressions to be included in a sematnic type. The purpose of this features is to allow one to specialize certain concepts to more accurately annotate objects, without having to go through the process of creating a new ontology, or editing an existing one. These concept definitions are expressed using OWL[2]. |
| At line 170 added 1 line. |
| + ---- |
| At line 171 added 1 line. |
| + [#1] We note that actor ports may not always be represented as an identifiable resource, and instead may be modeled as components of an actor. For example, consider an actor ''A'' having two ports ''P1'' and ''P2''. For the case where ''P1'' and ''P2'' are not separate resources, we can define the structural type of ''A'' as having two attributes {{P1}} and {{P2}} where {{A.P1}} denotes port ''P1'' and {{A.P2}} denotes port ''P2''. |
| At line 172 added 1 line. |
| + [#2] Perhaps originally converted from a Sparrow expression. |
| Removed line 174 |
| - [#1] Perhaps originally converted from a Sparrow expression. |
| Removed line 176 |
| - [#2] We note that actor ports may not always be represented as an identifiable resource, and instead may be modeled as components of an actor. For example, consider an actor ''A'' having two ports ''P1'' and ''P2''. For the case where ''P1'' and ''P2'' are not separate resources, we can define the structural type of ''A'' as having two attributes {{P1}} and {{P2}} where {{A.P1}} denotes port ''P1'' and {{A.P2}} denotes port ''P2''. |
| Line 178 was replaced by line 179 |
| - !!! Comments |
| + [Comments|KRSMSSemanticAnnotationComments] |
