TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I agree with you, and I'd call it a key-value pair.
I've seen this kind of terminology referenced for configuration files (registry or otherwise).
I hope this answers your question.
------------------------------------------------
Rebecca Downey, Matrox Imaging
-----Original Message-----
From: techwr-l-bounces+rdowney=matrox -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+rdowney=matrox -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of hannah -dot- drake -at- formulatrix -dot- com
Sent: June-11-2014 2:18 PM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Documenting XML/XML Terminology
Hi all,
We "polish up" developer release notes, and I'm wondering what the proper term is to describe a code string. My writers keep calling it "new key", but after doing some reading, it looks like "new key value pair" would be more correct.
Thoughts? In that case, would it be key value pair, key-value pair, or key/value pair? Or name/value pair?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Doc-To-Help 2014 v1 now available. SharePoint 2013 support, NetHelp enhancements, and more. Read all about it.
