Jonatan cannot participate today

[Jonatan Lundin <Jonatan.Lundin@citec.com>]

Hi,
I cannot attend this time either :-( But I still am struggeling with the definitions of the different table columns. Could we try to make a definition of the different columns?

A suggestion:
* "Main information" column shows the information required (must/shall) by a particular user in the lifecycle. This means that task oriented info always must be in the Main information column?
* "Referenced information" shows not mandatory information, but referenced from the main information and if the referenced information is used depends on the user knowledge. Most probably the referenced info is of type descriptive (concept/reference). The referenced info is most probably referenced from several life cycles and many user/target groups are using the info, whereas the Main info is most often only used by a specific user in a life cycle.
* "Main document" column shows a typical deliverable where the Main information is packaged/organized into. This implies that the deliverables in Main document must carry names such as "document", "manual", "guide", "book", "on-line help". "IETM" etc? Types like "Manufacturing Instruction"  (production life cycle) is then not valid since that is a Main info type of information?
* "Referenced document" columns shows deliverables that are not tied to a particular life cycle but are used in several life cycles. If the same type of info is needed across several life cycles my experience is to organize it into a specific deliverable to not repeat the same info in several, life cycle specific Main documents (even though this is not a problem in a DITA reusing world). Also the names of deliverables in Referenced documents shall carry names like "document", "manual", "guide", "book", "on-line help". "IETM" etc?

Please suggest for alternative interpretation of table columns if above is not applicable.

I would also argu that the "Customization" life cycle is after the "Production" since most often a customer/user is customizing (configuring/engineering) a product after it has been produced and delivered? To select which options and features the customer selects to purchase belongs to the Sales life cycle (and thus to customize is not to select which options/features to buy)?

Also in Customization life cycle I miss types like "Application descriptions" and "functionality descriptions". Ther user needs descriptions on the applicability of a certain feature/component and its principle of operation. Maybe "Product specifications" is covering this?

Br,
Jonatan
________________________________________
From: jang@jang.nl [jang@jang.nl]
Sent: Tuesday, March 16, 2010 12:34 PM
To: dita-machine-industry@lists.oasis-open.org
Subject: [dita-machine-industry] Regrets

Hi everyone, I am working on-site somewhere and cannot attend the meeting today. I'll be back at the next phone conference.

Jang