Re: So now we are content engineers?

Subject: Re: So now we are content engineers?
From: Joe Pairman <joepairman -at- gmail -dot- com>
To: Milan DavidoviÄ <milan -dot- lists -at- gmail -dot- com>
Date: Sat, 9 Nov 2013 05:18:07 +0800

I found Joe Gollner's original definition, though he's updated it since
then: "The application of rigorous engineering discipline to the design,
development, and deployment of content management and processing systems." (
http://www.slideshare.net/jgollner/introduction-to-content-engineering-cci2008.)
You could look at Joe's blog (
gollner.ca ) for his current thinking. And Mark Baker summarizes his own
content engineering principles here: http://spfe.info/spfe-principles/ .

As for me, I'm too busy to write much, but here was my take on one
particular aspect of structured content:
http://blog.joepairman.com/2013/04/is-structured-content-missing-a-trick.html


On Sat, Nov 9, 2013 at 4:56 AM, Milan DavidoviÄ <milan -dot- lists -at- gmail -dot- com>wrote:

> Hmm... "principles of content engineering". I wonder what those might look
> like.
>
> --Milan DavidoviÄ
>
> Sent from my Yost 10
>
>
> On Fri, Nov 8, 2013 at 3:47 PM, Joe Pairman <joepairman -at- gmail -dot- com> wrote:
> > Joe used it to refer to the application of engineering principles
> > to the design of end-to-end content processes and the accompanying
> > technologies (I'm paraphrasing but that's the gist of it). Mark Baker
> seems
> > to define it in a similar way in his final paragraph.
>


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.

Learn more: http://bit.ly/ZeOZeQ

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives


References:
Best places to put topics when they're needed twice: From: Editor in Chief
Re: Best places to put topics when they're needed twice: From: Gene Kim-Eng
Re: Best places to put topics when they're needed twice: From: Editor in Chief
Re: Best places to put topics when they're needed twice: From: Gene Kim-Eng
Re: Best places to put topics when they're needed twice: From: Editor in Chief
Re: Best places to put topics when they're needed twice: From: Gene Kim-Eng
Re: Best places to put topics when they're needed twice: From: rebecca officer
Re: Best places to put topics when they're needed twice: From: Gene Kim-Eng
Re: Best places to put topics when they're needed twice: From: Kathleen MacDowell
So now we are content engineers?: From: Erika Yanovich
RE: So now we are content engineers?: From: Lippincott, Richard
Re: So now we are content engineers?: From: Milan Davidović
Re: So now we are content engineers?: From: Joe Pairman
Re: So now we are content engineers?: From: Milan Davidović

Previous by Author: Re: So now we are content engineers?
Next by Author: Re: So now we are content engineers?
Previous by Thread: Re: So now we are content engineers?
Next by Thread: RE: So now we are content engineers?


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads