[sc34wg3] TMRM issues for 31 July 2005 (Montreal)

[Patrick Durusau]

This is a multi-part message in MIME format.

--Boundary_(ID_eOUjXic7cTP05o6uWBdVFA)
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT

Greetings!

The issues list for the TMRM (culled from email and other discussions) 
is attached.

Suggested process is to walk through the current draft and take up the 
issues as appropriate. (There are other issues already noted in the 
draft and no doubt others will arise as we go through it.)

The editors will be producing a version of the current draft that 
incorporates the issues and any resolutions directly in the draft for 
ease of reference.

Hope everyone is having a great day!

Patrick

-- 
Patrick Durusau
Patrick@Durusau.net
Chair, V1 - Text Processing: Office and Publishing Systems Interface
Co-Editor, ISO 13250, Topic Maps -- Reference Model
Member, Text Encoding Initiative Board of Directors, 2003-2005

Topic Maps: Human, not artificial, intelligence at work! 


--Boundary_(ID_eOUjXic7cTP05o6uWBdVFA)
Content-type: text/plain; name=TMRM_Montreal05_Issues.txt; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Content-disposition: inline; filename=TMRM_Montreal05_Issues.txt

TMRM Issues - Montreal 2005

1. Order of presentation.

Suggested that proxies are defined in terms of properties, which are
not yet defined, etc.

2. Terms and Definitions

Suggested new ordering:

Sets

Operators

Predefined set operators

Logical operators

(typos and errors to be fixed by the editors)

3. Property defined as key/value pair.

Definition is seen by some as contrary to customary practice.

Compounded by later reference to "labeled values," causing one reader
to remark: "I see the label and value, so where is the key?"

4.. Values are unconstrained.

a. Underdefined
b. Should say all values are typed

5. Atomic vs. Opaque for values

Either term means that the TMRM is unaware of any value
structure. Exist (or not) as defined by a disclosure but that is
beyond the TMRM.

6. Proxies defined using natural numbers.

Seen as:

a. Redefining semantics of TMDM
b. Serves no purpose
c. Distorted definitions
d. Should the TMRM have built-in proxies? (It being suggested those
should be in disclosures.)
e. Would defined property classes work as well? Allowing disclosures
to define proxies with whaterver properties they deem appropriate for
the property classes. TMRM defines proxies for them for the path
expressions in the TMRM. If users don't define them in their SMDs,
then those path expressions are not available to them. 

7. Multiple (identical) keys in a single property? Why disallowed?

8. Why does values(x) produce a bag? (Why not a different notation to
   denote a bag?)

9. Proxy merge/view function defined on proxy? Shouldn't that be on
   the map? Interaction with id() function?

--Boundary_(ID_eOUjXic7cTP05o6uWBdVFA)--