The main reason for adopting DITA is its support for reuse. Reuse implies context, it means using the same thing in different situations, in different contexts. But in the same time we want people to interact with the DITA content as if they are using a word processor, so ignoring the context information. How we can control the context, when we should hide it and how we should do that, because we cannot remove it even if we hide it.
Attendees will understand that reuse benefits do not come without a cost and that cost relates to the complexity created by managing the context for DITA.
We will try to define what context means for DITA and understand the inevitable requirement to define formally a DITA project that should express all the deliverables we want to obtain, thus materializing the possible contexts.
An analysis of when context should be hidden and when it should be made explicit will be provided and we will discuss possible solutions to still be aware of the context even if that is not visible to the casual users or to present the context and allow full context management for the advanced users that are aware of reuse and thus different contexts.