OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-machine-industry message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Notes from face-to-face meeting DITA Europe 2011


Hi all,
My brief notes from the face-to-face meeting 17:00 - 18:00 in Hotel Mariott, Prague 8 Nov.

Participants:
Jonatan Lundin
Jang Graat
Keld Jellesen
Markus Abt (instead of Sissi Closs)
Jarno Kaapu (observer from Sandvik Mining and Construction)

 

  • We discussed the previous year (from last DITA Europe in Nov 2010). The ambition for the past year was to listen to the community to get feedback on the requirements for DITA 1.3. Jonatan has set up a DITA machine industry LinkedIn group which has some 88 members. Jang has set up a DITA forum on http://www.ditadocs.com/forum/ where requirements etc for DITA 1.3 machine industry can be discussed. These environments have been advertised on dita.xml.org, via DITA yahoo group and on LinkedIn. So far the DITA community has put little interest in stating any requirements. Machine industry members are asked to share knowledge in these environments.
  • The meeting in Prague decided to change approach for the coming year.
  • Instead of waiting passively for requirements, we, as a group and individual specialists, must actively make suggestions/proposals based on what we know about machine industry needs.
  • This new approach doesn't necessarily mean that we must make new specializations. A sound approach is to make a white paper about how the existing DITA 1.2 architecture can be used to manage machine industry specific content, such as maintenance plans etc.
  • We agreed to make such a paper, looking at existing implementations of a maintenance plan. Keld, Jang and Jonatan have examples of how DITA is used to manage such content. Jarno also has examples. We agreed to look at four examples and conclude on what is common etc. Members of the group are asked to provide samples of maintenance plans.
  • A white paper may give advice on how a specialization is carried out to manage specific requirements, meaning that we do not need to develop the specification, but describe it.
  • If the group finds it necessary, also a specialization is developed. There are political/market share reasons to put in machine industry markup in DITA 1.3 (even though it is only few elements), to give the technical community a sense that DITA is a true machine industry architecture. A specialization does not have to be perfect; merely it should provide a starting point for users.
  • A work group meeting should be held as a face-to-face meeting somewhere. If a whole day can be reserved, we will achieve great work. To use the phone conferences as a “solution meeting” is not working.
  • The focus is on maintenance plan and technical data information types. Also spare part content and possible also troubleshooting information types is in priority for the coming year.
  • Jonatan will check if/how Jarno can join the group as an observer.

Something I missed?

 

Best regards,

Jonatan



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]