DNER Architecture

DNER Usage Scenario Issues

Case one introduces the concept of DNER kite marking. Is DNER kite marking simply a specific example of a ratings service? Is being listed as part of the DNER an implicit kite mark?
Case one discusses the end-user 'highlighting' parts of a resource. Is the ability to highlight an important feature of the DNER information environment? Should the architecture support shared, cross-media, cross-DNER highlighting?
Case one introduces the notion of a 'link basket' - a persistent personal collection of DNER resources. Is a DNER link-basket middleware service required?
In some cases, end-users may want to work at a sub-item level, i.e. to work with parts of items that are smaller than the items discovered using and delivered by the DNER presentation service. Examples include paragraphs of text, small video clips and cropped images. Should the ability to do this be a feature of the DNER architecture?
Case three introduces the notion of a common thesaurus. Should the architecture support access to thesauri services?