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 found many references to
>"stringified" and "stringify", for example "stringified full entity names".
>...From context, it appears to mean an entity name that has become a string
>(stringified), or the process of turning an entity name into a string (to
>stringify).
>
>Does anyone else have info on how long this coinage has been in use, and how
>wide its acceptance is?
Idunno how long the expression has been in use, but in my little corner
of the planet, it's common and widely accepted. I document CORBA-compliant
software tools and I've included a small excerpt from the OMG's CORBA spec
as an example of the word's use. (Hey, I didn't say it wasn't ugly!)
HTH!
-Sue Gallagher
susan-gallagher -at- vertel -dot- com
------- From the CORBA Specification ----------------
------- see www.omg.org for more info ---------------
CORBA V2.3 An Information Model for Object References June 1999 13-21
13.6.6 Stringified Object References
Object references can be ?stringified? (turned into an external string
form) by
the ORB::object_to_string operation, and then ?destringified? (turned back
into
a programming environment?s object reference representation) using the
ORB::string_to_object operation..
There can be a variety of reasons why being able to parse this string form
might not help make an invocation on the original object reference:
? Identifiers embedded in the string form can belong to a different domain
than
the
ORB attempting to destringify the object reference.
? The ORBs in question might not share a network protocol, or be connected.
? Security constraints may be placed on object reference destringification.
Nonetheless, there is utility in having a defined way for ORBs to generate and
parse stringified IORs, so that in some cases an object reference stringified
by one ORB could be destringified by another.
To allow a stringified object reference to be internalized by what may be a
different ORB, a stringified IOR representation is specified. This
representation instead establishes that ORBs could parse stringified object
references using that format. This helps address the problem of bootstrapping,
allowing programs to obtain and use object references, even from different
ORBs.
The following is the representation of the stringified (externalized) IOR:
<...>
------------------ end included text -----------------------------
