Change Log

Change Log for DI Working Group Authoring Scenarios Document

Notes

There is one sheet in this spreadsheet for each version of the Authoring Scenarios document. Each change is logged against the version at which it was raised and is given a number based on the date of that version. General items, that apply across multiple versions, are recorded in the General sheet. Each item has a description, a status, the event or comment that caused it to be raised and details of the version of the document in which it is finally resolved. The status of an item is subject to review at any time. For example, where an item is shown as No Change, this does not imply that it may not be raised for further discussion. Likewise, where an item's status is shown as Complete, that assertion can always be challenged.

The following list describes each status value

Accepted: The item is accepted and the document will be updated accordingly
No Change: The item is not accepted. No change will be made. Items in this state can, of course, be reviewed at any time.
In Progress: Work on the item is in progress
Complete: The item is accepted and the document will be updated accordingly
Investigate: Further investigation of the item is required before it can be completed
Addressed by: The item is addressed by the changes to another item that is cited in the status entry

General Items

Identification	Description	Status	Source
General-001	Review output of delivery context workshop to extract authoring scenarios related information	Accepted	DIWG F2F Ottawa
General-002	Review the charter definition of the Authoring Scenarios document	Accepted	Rhys
General-003	Review the commonality with accessibility. Cross reference to Delivery context	Accepted	Rhys
General-007	Upload the document to the appropriate part of the member web site	Accepted	Rhys
General-008	Sort out references to previous versions after upload	Accepted	Rhys
General-016	Should we be using delivery context rather than device in sections 4 and 5?	Investigate	Rhys, Lalitha, Luu

Responses to Version 2002-06-17

Identification	Description	Status	Source
020617-003	Show the derivation of each individual definition and requirement from the concrete examples	Accepted	Stephane Maes
020617-005	Specific examples and perhaps subsection on repurposing	Accepted	Stephane Maes
020617-007	Different granularity of synchronisation	Investigate	Stephane Maes:
020617-008	Change the number of channels or synchronisation granularity. Check if multimodal=multiple channels in our current glossary	Investigate	Stephane Maes
020617-010	Details for the discussion of application options that improve accessibility	Accepted	Stephane Maes
020617-011	Complimentary vs Supplementary applications	Investigate	Stephane Maes

Responses to Version 2002-06-24

Identification	Description	Status	Source
020624-009	Discuss the data that flows between different authoring roles	Accepted	DIWG F2F Ottawa 2002-06-28
020624-018	Discuss notion of standard API's for tools	Investigate	DIWG F2F Ottawa 2002-06-28
020624-019	Discuss notion of testability and testing challenges. May not be much that DI can offer in practice	Accepted	DIWG F2F Ottawa 2002-06-28
020624-021	Discuss tools in the affordability section and API's – Don't have good notes on this	Investigate	DIWG F2F Ottawa 2002-06-28

Responses to Version 2002-07-14

Identification	Description	Status	Source	Version where Resolved
020714-001	Add material for Roland's note on aggregation and portals/portlets to the section on applications and content. Roger's point that even images already constitiute a structure where the specialisation of the contained object is different from the specialisation for the page.	Accepted
020714-002	Explicitly discuss new and existing applications in the Scope section.	Investigate	Lalitha, Axel
020714-008	Include scenarios in the Interactions between roles section	Accepted	Lalitha
020714-047	Summarise those characteristics that are important for DI (AS or DCO?)	Investigate	Rotan
020714-048	Should the Scope section be called Goals to be in line with DIP?	Investigate	Luu
020714-049	Mention author roles when discussing authoring implications in sections 3 to 6	Accepted	Luu
020714-050	Provide specific labels for particular DI implications in the spirit of those in the DIP	Accepted	Luu
020714-051	Review use of SHOULD and MUST throughout lists of implications for approaches to DI	Accepted	Luu
020714-056	Add a graphic in Interactions Between Roles	Accepted	Luu
020714-059	Use resource rather than asset	Accepted	Luu
020714-062	Use content creator rather than author in 3.3.1	No Change	Luu	2002-09
020714-064	Use content creator rather than author in 3.2.2	No Change	Luu	2002-09
020714-065	Use content creator rather than author in 3.2.3	No Change	Luu	2002-09
020714-067	Add requirements to Device Diversity	Accepted with modification	Luu
020714-068	Need a proper link to PWD in Shared Bookmarks	Accepted	Luu
020714-069	Add requirement for backwards compatibility	No Change	Luu
020714-070	Change the definitions of specific designers. Add notion of a device designer role	Accepted with modification	Axel	2002-09
020714-071	Resolve the distinction between navigation design and interaction design	No Change	Axel, Shlomit	2002-09
020714-072	Discuss the integration point between content creation and business logic	Investigate	Axel
020714-073	Improve description of non-interactive application	Completed	Axel, Shlomit	2002-09
020714-074	Add note about classification of devices	Investigate	Axel
020714-075	Streaming media is out of scope	Investigate	Axel
020714-076	Broad assumptions about usability	Investigate	Axel
020714-077	Measure of usability of devices is key	Investigate	Axel
020714-078	Classification of devices by usability is needed	Investigate	Axel
020714-079	Move the stylistic designers section	No Change	Shlomit	2002-09
020714-080	Remove the note about overlap of content creation with stylistic design	Accepted	Shlomit
020714-081	Remove the summary from section 2	Accepted	Shlomit
020714-082	Add consideration of navigation changes when moving from graphic to audio presentation	Investigate	Shlomit
020714-083	Add comment on supporting transformation of menus for linear presentation such as audio	Investigate	Shlomit
020714-084	Add comment about raw application data from the client	Investigate	Shlomit
020714-085	Question about the need to hide device capabilities in 4.1.2	Completed	Shlomit	2002-09
020714-086	Question about ability to support as yet unannounced devices	No Change	Shlomit	2002-09
020714-087	Add discussion of viewing distance to 4.2.1.1	Completed	Shlomit	2002-09
020714-088	Mention personalisation in 4.2	Completed	Shlomit	2002-09
020714-089	Comment on frequency of change of personalisation information	Completed	Shlomit	2002-09
020714-090	Change of location changes language - 4.2.2.2	No Change	Shlomit	2002-09
020714-091	Is location in scope at all?	No Change	Shlomit	2002-09
020714-092	The transaction continuation scenario may be flawed	No Change	Shlomit	2002-09

Responses to Version 2002-07-29

Identification	Description	Status	Source	Version where Resolved
020729-002	Add a scenario that includes a printer	Accepted	Rotan
020729-004	Add discussion of presentation-independent markup in dynamically acquired data in section 3.8	Accepted	Lalitha