OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [dita] FW: Why "Key name"?



I'm not sure I see the need either. "Key" and "key reference" are parallel to "ID" and "ID reference", as Eliot points out. And that's sufficient for the majority of cases, where the keyref is to a simple key, not a compound value. So I don't think the problem case is all that big.

I'm also not sure how, even if there is a problem, adding "name" helps.   Maybe we could see an example of a problem sentence, written both ways?

Michael Priestley, Senior Technical Staff Member (STSM)
Lead IBM DITA Architect
mpriestl@ca.ibm.com
http://dita.xml.org/blog/25


From: ekimber <ekimber@reallysi.com>
To: "Ogden, Jeff" <jogden@ptc.com>, dita <dita@lists.oasis-open.org>
Date: 11/04/2009 11:20 AM
Subject: Re: [dita] FW: Why "Key name"?





The question in this thread is whether anyone objects to Jeff's general
review comment that the term "key" should be replaced by "key name" in all
discussion of key-based addressing, as in "a key reference can use a key
name together with an ID" rather than "a key reference can use a key
together with an ID".

My initial reaction was that "key name" isn't any better than "key" and that
keys are not in fact names (because "name" implies non-uniqueness but keys
are unique, meaning they are a form of identifier, not a form of name). But
that is clearly pedantic hair splitting.

Jeff's intent, if I understand it correctly, is to more clearly distinguish
references to keys from "keyref", which in most contexts is the combination
of the reference to a key [name] and, optionally, the ID of an element
within the topic ultimately addressed by the key. Thus, there could be some
confusion between the phrase "key reference" (by which I mean a reference to
a key) and "keyref" (the attribute), which involves both a key reference and
an (optional) ID reference.

As indicated in the discussion copied below, while I don't think Jeff's
terminology change is needed I don't see it as hurting either. But I didn't
want to unilaterally accept or reject Jeff's suggestion without
consideration by the TC as a whole.

If there's no serious objection I will use "key name" in place of "key" as I
work through comments on the linking and addressing parts of the spec.

Cheers,

Eliot

On 11/3/09 9:24 AM, "Ogden, Jeff" <jogden@ptc.com> wrote:

> FYI
>
>  
>
>>> -----Original Message-----
>
>>> From: ekimber [
mailto:ekimber@reallysi.com]
>
>>> Sent: Monday, November 02, 2009 5:17 PM
>
>>> To: Ogden, Jeff
>
>>> Subject: Re: Why "Key name"?
>
>>>
>
>>> On 11/2/09 5:48 PM, "Ogden, Jeff" <jogden@ptc.com> wrote:
>
>>>
>
>>>> Key References are references to Key Names plus an optional
> sub-element
>
>>>> ID, so Key References are not just references to Key Names.
>
>>>
>
>>> I think I see the distinction you're trying to make, but I think
> it's a
>
>>> side effect of poorly-titled topics and imprecise descriptions of
> attributes
>
>>> and addressing.
>
>>>
>
>>> However, in trying to describe what the language *should* be I've
> convinced
>
>>> myself that while "key name" is no *better* than "key" it's no worse
>
>>> either and might help some readers make sense of the less-than
> optimal
>
>>> language in the 1.2 spec.
>
>>>
>
>>> So I won't object to your suggestions. However, I would feel better
>
>>> about it if the language change was brought before the TC for
> approval.
>
>>>
>
>>> Cheers,
>
>>>
>
>>> E.
>
>>> ----
>
>>> Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc.
>
>>> email:  ekimber@reallysi.com <
mailto:ekimber@reallysi.com>
>
>>> office: 610.631.6770 | cell: 512.554.9368
>
>>> 2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403
>
>>>
www.reallysi.com <http://www.reallysi.com>  |
>
>>
http://blog.reallysi.com
>
>>> <
http://blog.reallysi.com> | www.rsuitecms.com
>
>>> <
http://www.rsuitecms.com>
>
>>
>
>> -----------------
>
>>
>
>>> -----Original Message-----
>
>>> From: Ogden, Jeff
>
>>> Sent: Monday, November 02, 2009 5:48 PM
>
>>> To: 'ekimber'
>
>>> Subject: RE: Why "Key name"?
>
>>>
>
>>> Key References are references to Key Names plus an optional
> sub-element
>
>>> ID, so Key References are not just references to Key Names.
>
>>>
>
>>>    -Jeff
>
>>
>
>> ----------------
>
>>
>
>>>> -----Original Message-----
>
>>>> From: ekimber [
mailto:ekimber@reallysi.com]
>
>>>> Sent: Monday, November 02, 2009 4:36 PM
>
>>>> To: Ogden, Jeff
>
>>>> Subject: Re: Why "Key name"?
>
>>>>
>
>>>> On 11/2/09 5:25 PM, "Ogden, Jeff" <jogden@ptc.com> wrote:
>
>>>>
>
>>>>> The key thing for me is that we pick one or the other and stick
> with it.
>
>>>>> And I happen to prefer "key name" over "key" because it seems a
> little
>
>>>>> clearer and reads a bit better.  For example having "Key
> Reference" and
>
>>>>> "Key Name" seems to be more parallel and clearer than having
> "key
>
>>>>> reference" and "key".
>
>>>>
>
>>>> But a key reference is a reference to a key, just like an ID
> reference
>
>>>> is a reference to an ID. We don't say reference to an ID name.
>
>>>>
>
>>>> I'm afraid I'm not buying your argument.
>
>>>>
>
>>>> The notion of unqualified "key" in the sense of something you look
> up seems
>
>>>> pretty well established in computer science.
>
>>>>
>
>>>> It just seems like an odd terminology change to make now.
>
>>>>
>
>>>> Cheers,
>
>>>>
>
>>>> E.
>
>>>>
>
>>>> ----
>
>>>> Eliot Kimber | Senior Solutions Architect | Really Strategies,
> Inc.
>
>>>> email:  ekimber@reallysi.com <
mailto:ekimber@reallysi.com>
>
>>>> office: 610.631.6770 | cell: 512.554.9368
>
>>>> 2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403
>
>>>>
www.reallysi.com <http://www.reallysi.com>  |
>
>>>
http://blog.reallysi.com
>
>>>> <
http://blog.reallysi.com> | www.rsuitecms.com
>
>>>> <
http://www.rsuitecms.com>
>
>>
>
>  
>

----
Eliot Kimber | Senior Solutions Architect | Really Strategies, Inc.
email:  ekimber@reallysi.com <
mailto:ekimber@reallysi.com>
office: 610.631.6770 | cell: 512.554.9368
2570 Boulevard of the Generals | Suite 213 | Audubon, PA 19403
www.reallysi.com <http://www.reallysi.com>  | http://blog.reallysi.com
<
http://blog.reallysi.com> | www.rsuitecms.com <http://www.rsuitecms.com>


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]