Finnish comments on document  XX Enterprise viewpoint


1. page 3, line 7

   Does this refer to chapter 11? What is the role of the concrete
   application architecture? Is is an use-case of the guidelines?

2. Clause 3.2. 

   The classification of related terminology was initially intended to be
   an informal way of getting people to think about the scope of
   enterprise viewpoint. We feel, that the classification is not
   essential contents of the standard itself.

3. Page 5, policy. 

  The terminology on specification community, community policies and
  internal policies, even ODP systems is not expressed clearly enough.
  We suggest the use of terms community, community contract, domain,
  domain policy. Domain policies must be negotiated against each other to
  produce a community contract.

4. Clause 6.3. 

  We feel that deontic thinking can be here limited to two levels: 
  - right (to be lawful) to do thing
  - ability to do things (to have means) 
  Other variations can be achieved by exploiting these levels
  recursively on the recursively defined ODP systems, and of cause by
  playing games with negotiations.

5. Clause 6.3, resource domain

   Replace by resource management domain, keep definition.

   Delete the rule on lines 25-28
 
   Add requirement on line 20 that a resource belongs to 1 domain.


6. page 6, line 11

   Guarantee refers to contract, but a different word is needed in order
   to avoid cyclic definitions.

   Service is an abstraction of behaviour. See definition of behaviour
   is Part 2. Leads to a set of potential activities offered by objects.
   Has also the feeling of a package of interactions: having a haircut
   and paying for it.

7. Clause 6.4., line 21, artifact role

   An artifact role should be defined as a role that never initiates an
   activity, instead of a role that never performs any activity.

   Object actions (methods) are of no interest here.

8. Page 6, line 25, delegation

   Define delegation as the transfer of a role. The transfer
   of role includes the transfer of obligations and authorities.

    Delegation to an agent.

9. Page 6, line 36 and page 7


   Join objective and purpose. 

10. page 7, line 21

   Rather use QoS in ODP work here.

11. pages 7- 8

   Delete definitions of user, act, agent, person and scope

12. page 9

   This kind of text is preferred earlier in the document.

13. page 10

   We have concerns on Figure 1 and would suggest it to be redrawn. It
   is not in conformance with the text and in our opinion has some
   faulty assertions.

14. page 10, questions

   line 23 & 24: specify as epochs
   line 25: No


15. Page 11, lines 2-5

   The object state and behaviour form a duality.

16. page 13, lines 21-23, 24-25

   Incorrect statements.

17. page 15, lines 27-39;
    page 16, lines 8-9, 24-26, 31-32 

   Incorrect statements

18. page 17, lines 1-4

   ???

19. clause 10

   It is improbable that this clause is filled within the time allowed
   for the development of this standard. We suggest, that the current
   clause is moved to an annex and NBs are requested for contributions.