3 responses to “Containing Content

  • EditorEtc™ LLC

    Reblogged this on EditorEtc and commented:
    Ain’t it the truth.

  • Julieta Lionetti

    Hi, I think that when they say content without container, they are mostly thinking in data-base publishing, and they are thinking in the data-base, not in publishing whatever is in the data-base. Because after being published, you’ll have a product and the product needs a container. Your html/css for a blog is also a container.

    I’m trying to understand what they are saying and not succeeding at it. Are they thinking publishing as if it only were processes and endless iterations? Too geeky for my understanding. I’m still a reader. A human one, I mean.

    Are they thinking publishing in the same terms of search?

    Liked you post. Much necessary.


  • mmcnamara49

    A late reply, as I always seem to be catching up with my reading. Anyway as a comment on your post, I feel that content will always reside in a container of some sort, somewhere. Two examples from some projects that I am working on, database publishing and technical publishing.

    From a database publishing point of view, I don’t think you could get more ‘containerised’ content if you tried. This project relates to a large parts/component catalogue publisher, all of the data ‘lives’ in a number of database ‘objects’. Each ‘content’ object can be edited as can associated the associated ‘Metadata’. When it comes to publishing of the content, the relevant objects are exported from the database and sent via various ‘formatters’ depending on the style of the final content and end up in ‘new’ containers, be that PDF pages, printed data sheets, web pages or ‘the’ printed catalogue itself. A newer addition to the publishing pipelines is the ability for an ‘end-customer’ of the content owner performing a search on the database and requesting information contained in the various database ‘containers’ to be delivered to them as a PDF (container) or ePub ebook (container). I suppose you could classify this as a ‘service’ approach as the content owner will be charging for this extra ability.

    The other project also shows that content will live in a variety of ‘containers’ during its life cycle. I am Project Managing this one where content has been living in a 30 year old Word processing system (WPS) as plain ASCII files and generally having been only printed to paper (latterly a PDF driver was introduced) – all very monospaced! The project covers moving the ASCII content into a particular XML specialisation – S1000D (container) – for the client to load into its newly commissioned database (container) where it will be combined with other XML content and metadata. Eventually the content will be ‘published’ as IETM’s (Electronic Technical Manuals) (container) for world-wide end-users who will if required, print pages to paper ‘locally’ if required.

    So yes I can see a lot of different ‘containers’ being used along any publishing ‘pipeline’, although I am not sure I would truly class the original WPS ASCII content in the above example as being in a ‘container’ but there in lays the different interpretations of ‘what is a container’, after all isn’t HTML just plain ASCII with tags!!!

    Hope this adds to the discussion.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: