“We expect iiRDS to become the standard for the exchange of documentation in Germany and to expand successively into the rest of the world” – with these words Volker Römisch expresses his vision for iiRDS. What further goals he wants for the standard, you will learn in the interview directly from himself!
“We are shaping the future of the intelligent use and reuse of information,” says Joe Pairman in an interview concerning iiRDS. The answer to find out what this exactly means and what the iiRDS consortium wants to achieve is only one click away…
“Today many component content management systems are naturally based on XML – our wish is that in three years a large number of these systems will also use iiRDS naturally”, Ulrike Parson and Mark Schubert tell us. What other visions and wishes they have for iiRDS, you can find out in the interview…
“After three years of development, iiRDS could be regarded and respected as an international standard,” says Yangsook Kim, telling us in an interview why she thinks so highly of the standard for providing intelligent user information.
Are you also “iiRDS ready”? In an interview, Andreas Klüter shares his views on his participation in iiRDS and gives an exciting outlook on the changes that the standard may soon bring with it.
In the second part of our blog series “Five Questions to…” Dr. Matthias Gutknecht is our conversation partner and reveals what drives him to cooperate on iiRDS.
In this first interview of our new and exciting blog series “Five Questions for…” Christian Geiger, member of the iiRDS Consortium, talks about his motivation, his hopes and visions for iiRDS.
When you hear about iiRDS for the first time, it will probably seem quite complicated – it was the same for me. So to understand it better, let’s strip it down to a machine everybody knows from everyday use: Why not use a coffee machine in order to explain the highly technical standard?
Industry 4.0 and the Internet of Things (IoT) have changed technical documentation. Users now read small chunks of information that match their context, task, or role. Instead of classical documentation, we now need information that is modular, neutral with respect to format, and accessible via metadata and full-text search…