As part of my general philosophy of sharing information, help, problems etc., it has occurred to me that it might be a good idea to have a forum for discussing the S1000D Specification. This is particularly important right now with our Friends in the USA starting to come on board and beginning to look at using the Specification.
Judging from some of the emails that I have been getting there seems to be some difficulties in understanding some of the concepts of the Specification and how to apply it. The UK has been involved in producing information to this Specification for some years. Looking at the wide range of understanding how it should be applied, and what should be put where, this forum is a little overdue.
Sometimes I believe that I can be a little provocative by making statements which may seem to be calculated to start an argument - please forgive this behaviour in advance. It is intended to be thought provoking and not intended to get up peoples backs.
I hope that this forum will become a 'conversation' and look forward to any feedback and comments that might arise.
5 comments:
Why doesn't MEKON just have another unsactioned S1000D event. Isn't this what you really want to do?
I'm waiting for the S1000D discussion. My employer is just hearing about it so I wanted to appear smart! Help!
Martyn,
Very good idea to start this blog!
There is definitely a huge gap on the Internet concerning S1000D and information on its difficulties to get it implemented in the 'real world'.
I've just completed a first paper publication according to S1000D (as much as possible, that is) and although the specification is over 2000 pages, it is my feeling it lacks a lot of practical information and real world examples, instead of the scattered xml snippets. For example, it took me months to get an idea of what our paper publication of S1000D would look like and how it was going to be organized (TOC-wise).
Useful blog posts I can think of right now are some kind of practical "Getting Started" series, which discusses the steps one has to go through to create an S1000D publication (starting with e.g. "Is S1000D right for you?", "Choosing authoring, database and IETP software", "Creating a DMRL and business rules", "A comparison between a 'standard' technical manual and an S1000D technical manual: which information goes where" etc.)
With regard to putting links on this blog, I would suggest to not (only) link to MEKON, as this causes comments like the one above to appear. Perhaps it is more fair to link to either all S1000D software companies or to none...
Success!
Ward
I am working for Corena who creates different CSDB solutions. We are quite close to users and therefor understand exactly the problems arising.
However - as S1000D becomes more and more "the only" way of doing it right, the demand of exchanging practical information becomes higher.
We need to collect stories about succesful implementation of S1000D projects. So - I absolutely are in-line with Martyn
A getting started sereis would be great, especially a driect integration with Adobe Framemaker
Post a Comment