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.
Subject:RE: Is this some obscure but correct terminology? From:"Lisa Hickling" <Lisa -dot- Hickling -at- realsuitesoftware -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 5 Aug 2005 09:35:56 -0400
-----Original Message-----
From: Simon North
dehydration means converting an object instance through serialization
into an XML stream.
hydration, or more correctly rehydration, means converting a serialized
XML stream (back) into an object instance.
Frankly, he'd have been better off simply calling it serialisation, if
that's what he means. As it stands, the sentence is
actually meaningless - ASCII is a character representation not a format.
XML uses Unicode, of which ASCII is a subset,
so an (English) XML structure (whatever that might be - I assume he
means the instance and not the structure as defined by
the DTD or XML Schema) is most likely in ASCII anyway. Does he perhaps
means removing the markup to convert it to
raw ASCII and back? If so, he's not only barking up the wrong with tree
with terms hydration and dehydration - he's stumbling around in the
wrong wood.
------------------------------------
I'd have to agree with Simon's comment. "Serialization" is the generic
term for instance-to-instance conversion of objects to XML.
Deserialization describes the reverse. These terms will also be better
understood by wider XML audiences that are not necessarily Java oriented
(read: old Microsofties like me). If your entire audience definitely
uses XML within a Java context then you might use "dehydrate/rehydrate"
in accordance with Simon's definition. If not, then you have a case for
"serialize/deserialize".
As to the sentence's meaning, it's probably just developerOverSpeak
describing what already is implied in the simple words "serialize" and
"deserialize".
Lisa H.
GTA, ON
"The finest language is mostly made up of simple unimposing words."
George Eliot
(This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately.
Ce courriel est confidentiel et protege. L'expediteur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) designe(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immediatement, par retour de courriel ou par un autre moyen. )
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.