Re: [wsrp] [errata #22] Caching of preferredTitle

[Rich Thompson <richt2@us.ibm.com>]

I do not think this is something we
need to prescribe. A reasonable Consumer is going to cache this in order
to be able to display it when directly retrieving the markup from its cache.
Portlets may want to refresh this value separately from the markup, but
I would expect most to leave it unchanged when updating the cacheControl
for the Consumer. 

Rich Thompson

Rich Thompson/Watson/IBM@IBMUS 05/21/2003 12:16 PM

To:        WSRP OASIS <wsrp@lists.oasis-open.org>         cc:                 Subject:        [wsrp] [errata #22] Caching of preferredTitle

Comment: #22. 5/21/03 (Alejandro Abdelnur) 
Spec doesn't really define the relationship between markup and title. Is
title considered part of cache content? If yes, where does it say that
in the spec? I see assertions like if MarkupContext.useCachedMarkup is
true, then MarkupContext.markupString MUST be NULL. Why doesn't the spec
say that MarkupContext.preferredTitle would be NULL too in this case.

Document: Spec 
Section:  6.1.10 
Old Text: If the value for useCachedMarkup is “true” the markupString
and markupBinary fields MUST NOT be returned. 

New Text: If the value for useCachedMarkup is “true” the markupString
and markupBinary fields MUST NOT be returned. If the value for useCachedMarkup
is “true” the preferredTitle field SHOULD NOT be returned and the previous
preferredTitle value reused.