Tim’s Weblog Tim's Weblog
Tim Strehle’s links and thoughts on Web apps, managing software development and Digital Asset Management, since 2002.

Digital Asset Management Reading List Sep. 2017: Content Management, W3C schema.org group

Here’s the last month’s Digital Asset Management articles which had a lasting impression on me – picked from the constant stream of blog posts you can see float by on Planet DAM. For more curated DAM links, see the weekly Digital Asset Management.com Links and Tracy Wolfe’s 10 things on the 10th.

In August, one of the hottest DAM debates ever (60+ comments) takes place: On LinkedIn, David Diamond proposes calling our subject “Content Management” instead of “Digital Asset Management”. Ralph Windsor responds with Digital Asset Management is not Content Management, coining the term “Content DAM”, and he defines Digital Assets on his newly-launched Digital Asset News site. See also the trend to rebrand DAM products: David’s Picturepark article about Content Management 2.0, censhare’s Ian Truscott on Things, Stuff and Content, and Northplains’ Jason Arena on Content Lifecycle Management.

A glimmer of hope for better DAM interoperability is Emily Kolvitz initiating a W3C DAM Industry Business Ontology Community Group whose mission is “to propose, discuss, create and maintain extensions to schema.org related to the DAM industry”. She writes about it in Can we get some DAM Findability on the Web? Everyone, please participate! – “Standards-based” is one of ADAM’s four key attributes of interoperability, and Anna Cotton lists flexibility and integrations in her 5 questions to ask your DAM vendor.

Read the full article…

Tue, 19 Sep 2017 20:27:00 +0000

Web frontend integration: Just drop me a link

For two reasons, I think about software interoperability a lot (see Improving DAM Interoperability in 2017): First, software – especially “content hub”-style DAM systems – must work well with other software to help people do their jobs. The second reason is that when we consider splitting a monolithic (DAM) system into multiple smaller Self-Contained Systems, these parts need to interoperate with each other, too.

A very interesting aspect of interoperability is frontend integration: When in application A, people need access to information living in application B. How do they navigate from A to B? Can they see both application’s interrelated data on the same screen? I wrote about this in Web app interoperability – the missing link. Now it’s time for a few experiments.

Read the full article…

Sun, 10 Sep 2017 20:41:00 +0000