As I have no idea what this conversation is about (great way to open a
discussion in which I offer my thoughts!), I googled "round-trip" and
the Wikipedia definition says something along the lines of (no, wait,
it's actually a direct quote):

"The term round-trip is commonly used in document conversion
particularly involving markup languages such as XML and SGML. A
successful round-trip consists of converting a document in format A
(docA) to one in format B (docB) and then back again to format A
(docA?). If docA and docA? are identical then there has been no
information loss and the round-trip has been successful. More
generally it means converting from any data representation and back
again, including from one data structure to another."

Have I added anything to the conversation?  Or have I just told you
what you already know?

Dying to sit at the grown-ups table,


On 5/21/08, Kelly McDaniel <kmcdaniel at> wrote:
> IMHO roundtrip means: With two or more applications, changes made to a
> project in one application are reflected in both, and it implies that
> each application offers some exclusive functionality, and that there is
> some translation of some sort that transpires between the applications
> so that the changes reflected in the "other" application are rendered in
> that application's native method.

Reply via email to