This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27040 - Use the word "identity" in its ordinary English meaning
Summary: Use the word "identity" in its ordinary English meaning
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Data Model 3.1 (show other bugs)
Version: Last Call drafts
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Norman Walsh
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-14 02:23 UTC by C. M. Sperberg-McQueen
Modified: 2014-10-27 22:55 UTC (History)
1 user (show)

See Also:


Attachments
List of changes proposed (32.26 KB, application/xhtml+xml)
2014-10-14 02:23 UTC, C. M. Sperberg-McQueen
Details
Definitions of 'identity' and related terms from several desk dictionaries (10.36 KB, application/xhtml+xml)
2014-10-14 02:26 UTC, C. M. Sperberg-McQueen
Details
Revised list of change proposals (35.04 KB, application/xhtml+xml)
2014-10-27 17:53 UTC, C. M. Sperberg-McQueen
Details

Description C. M. Sperberg-McQueen 2014-10-14 02:23:42 UTC
Created attachment 1522 [details]
List of changes proposed

Most uses of the words "identity" and "identical" in our specs make sense to readers who approach them from the ordinary English meanings of the words; a few uses rely on a specialized usage of the terms which some WG members have reported is common in discussions of object-oriented programming.  Those passages make very little sense to readers who endeavor to understand them using the ordinary tools for establishing the meaning of words in a text, like dictionaries.

I propose that we reword some sections of our specifications to avoid relying on domain-specific meanings for terms not defined in our specifications.

I am opening this bug against XDM, but in fact the passages I believe we should change appear also in Functions and Operators, XQuery, XSLT, and XQuery Requirements and use cases; some passages in XPath might also be rephrased but I don't think they are urgent.

Attached is a list of passages I believe should change and proposed wording for each of them.
Comment 1 C. M. Sperberg-McQueen 2014-10-14 02:26:29 UTC
Created attachment 1523 [details]
Definitions of 'identity' and related terms from several desk dictionaries

The changes proposed rely on some claims about ordinary English usage of the terms 'identity', 'identical', etc.; this attachment supplies some documentation of those claims in the form of definitions found in an unsystematic survey of dictionaries.
Comment 2 C. M. Sperberg-McQueen 2014-10-27 17:53:02 UTC
Created attachment 1527 [details]
Revised list of change proposals

This revised list of changes adds alternate wordings to a few of the change proposals included.  The original proposals are unchanged.  Since there is no text in attachment 1522 [details] that is not repeated here, I'm marking the original attachment as obsolete.
Comment 3 Jonathan Robie 2014-10-27 22:18:36 UTC
Another alternative for XQuery and XPath Data Model 3.1: 2.3 Node Identity

Each node has a unique identity. The identity of a node is distinct
from its value or other visible properties; nodes may be distinguished
from other nodes even when they have the same values for all intrinsic
properties other than their identity.

(Atomic values do not have identity; The identity of atomic values, by
contrast, is determined solely by their intrinsic properties. No two
distinct integers, for example, have the same value; every instance of
the value “5” as an integer is identical to every other instance of
the value “5” as an integer.)
Comment 4 C. M. Sperberg-McQueen 2014-10-27 22:55:13 UTC
At the joint meeting today, the WGs discussed the changes proposed in the attachment.  Some amendments were made to some of the proposals (as recorded in the minutes of the meeting) and all changes were adopted either as proposed or as amended.  The list of optional changes and miscellaneous comments was recommended to the editors for their consideration; changes were left to the editors' discretion.

Accordingly, I'm marking this bug as RESOLVED / FIXED.