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: Replacement for "mix-and-match" From:Robert Lauriston <robert -at- lauriston -dot- com> To:Shawn C <shawn -at- cohodata -dot- com> Date:Fri, 6 Mar 2015 12:20:38 -0800
That doesn't help. I don't know what the difference would be if you
couldn't mix and match them.
Are "system models" some sort of building blocks, you can use as many
as are appropriate for a particular project, and they automatically
On Fri, Mar 6, 2015 at 11:20 AM, Shawn <shawn -at- cohodata -dot- com> wrote:
> Thanks for your reply Robert.
> Mix-and-match is being used in the literal sense. Meaning, all our system
> models can work together as a single cohesive unit. They are all compatible
> with each other.
> I hope this explanation gives you enough context.
> On Fri, Mar 6, 2015 at 11:15 AM, Robert Lauriston <robert -at- lauriston -dot- com>
>> "Mix and match widgets" and "inter-compatibility with all widgets"
>> don't seem like the same concept so it's hard to guess what you're
>> trying to say. Can you describe the functionality?
Adobe TCS 5: Get the Best of both worlds: modern publishing and best in class XML \ DITA authoring | http://adobe.ly/scpwfT