Finland votes "YES" for the progression of DIS14771 ODP Naming framework
with the following comments:

1. Clause 7.2 -- editorial/technical

   The section should include description of the possible outcomes of
   the name resolution process: success (found, not found), failure
   (could not resolve for some reason), unknown (technically successful
   but the result is not available because of name binding inconsistency
   or because of access restrictions). The same aspect is clearly stated
   in clause 9 for name comparison.

2. Clause 9 -- technical 

   The termination choice of "indeterminant" in the name comparison
   process should be split to two distinctive alternatives: one, that
   implicates that it is worth trying again (technical failure), and
   another that implicates that the retry is worthless (semantic failure
   or access denial). This distinction would be very useful for the
   realisations of federated, fault tolerant mechanisms.

3. Clause 5.2. -- minor editorial

   In the example given in Figure 1 and explained further in Table 1
   there are minor referential errors. For example, Table 1 refers to
   context 1 and context 2 that do not appear elsewhere.


4. Clause 6.13 -- editorial

   Continue the Note by giving examples of "ambiguity" and "another process":

   Examples of such alternative processes are homonym resolution and
   dynamic name resolution. Homonym resolution is a process which, for a
   given name, finds all entities designated by a homonym in a
   particular naming context. Dynamic name resolution is similar to name
   resolution, but it can provide a dynamically selected result for each
   invocation.

5. Clause 6.5 -- editorial

   Note 2 and the single note after the paragraph following note 2 are
   identical.

6. Clause 7.1. -- editorial

   Rewrite the paragraph under Figure 2.

   Thus name resolution is a sequence of transformations, each of which
   is dependent on the context it is performed in. Each transformation
   takes a name and produces a handle and a reminder. The handle
   determines the next transformation and the reminder is given to this
   transformation as the name to be resolved. Not all names are
   resolvable, but an entity may have multiple names. Not all entities
   are named in all contexts.

7. Annex B -- editorial

   Drop annex B. The material is too technical in relation with the main
   document. The concepts discussed do not appear elsewhere.

8. Annex D -- editorial

   Update references to standards and recommendations with appropriate
   numbers.