Metadata is a hot topic in technical documentation and is regularly discussed in presentations, articles and blog posts like this one. Interest in metadata in our industry therefore cannot be ignored, but why is this? Buzz words like “intelligent content”, “Industry 4.0”, “content delivery”, “PI class”, “iiRDS” and “artificial intelligence” are on everyone’s lips. These topics come up in different contexts, yet time and again all of them can be traced back to one common denominator – this ominous metadata. Who or what is it? Where does it come from? Who sent it? Does it come in peace? Will it take over the world? And what do I do if there doesn’t appear to be any of it? You’ll find out the answers to all these questions in this blog article! Continue reading
Experiencing SCHEMA first-hand – the reason behind our SCHEMA Conference since the very beginning. And what’s more, this is the only event in the TechDoc sector where this is fully possible. For us, this year is no different: we cannot wait to meet you, chat, eat and celebrate with you and discuss our products.
So, save the date: we would be delighted to welcome you to the NCC Mitte convention centre from 14 – 15 May 2019. Don’t miss this opportunity! Whether you’re a long-standing customer or a new face, everyone is welcome! Continue reading
What do SCHEMA and your weekend shopping have in common? – It’s simple: When you reach into that refrigerator in the comfortable air-conditioned supermarket, it’s very likely to contain several pieces of DAIKIN technology. DAIKIN is the world’s leading manufacturer of heat pumps, ventilation systems and air-conditioning and refrigeration systems. The multinational Japanese company with headquarters in Osaka and 67,000 employees worldwide offers solutions for hotels, office buildings and supermarkets, and also for domestic use. Plus: DAIKIN has chosen to use SCHEMA ST4 and the Content Delivery Server to create smart, interactive manuals. In their talk ‘DAIKIN Service Information at your service’ at the SCHEMA conference, Peter Lemahieu and Lore Vertongen explained why SCHEMA is the best solution for DAIKIN. Continue reading
Did you see us, by any chance? We were on the startlingly attractive stand 2/C07 in the exhibition area and there was always something going on! Out of a total of 4,600 visitors, we were able to meet many of them in person on our stand and present our products and new features. Continue reading
Who could do with a little more SCHEMA ST4 in their professional life? But only a little bit more? For example, maybe only the approval process is relevant to one colleague, while somebody else wants to be informed about publications and translations and another person just wants to request the creation of a single datasheet. SCHEMA ST4 is intentionally very comprehensive so that it can meet the demands of all the everyday tasks involved in the technical writing process. With workflow automation, you can make sure that colleagues only have access to the parts of our component content management system that they really need. Continue reading
You only need a few things for content delivery with SCHEMA: SCHEMA ST4, SCHEMA CDS, modular content and metadata. To tell you the truth, SCHEMA ST4 is not absolutely necessary here, but that’s a discussion for another time. For a long time now, SCHEMA ST4 has been your tool for creating intelligent modular content with taxonomies and metadata. One upload to the Content Delivery Server later and your content is also available via mobile apps or the browser, where it can be filtered according to target group. There are now some new features awaiting you in SCHEMA ST4 and SCHEMA CDS which make this process even smoother. Continue reading
When creating software documentation, one thing’s for sure: ensuring that interface terms in the software match the technical documentation presents a particular challenge for technical writers. If a term changes on the software interface, it must also be changed in the documentation. The same applies to adjustable values on the software interface, which are often changed just before development is complete. When there are several different versions of the software and the documentation, updating the changes is a cumbersome task which often involves a separate editing process. Continue reading