W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > May 2012

Re: mlw-lt-track-ISSUE-21 (cms-related-terminology): CMS related terminology: not only CMS as content [MLW-LT Requirements Document]

From: Dave Lewis <dave.lewis@cs.tcd.ie>
Date: Thu, 17 May 2012 12:14:49 +0100
Message-ID: <4FB4DDA9.4060906@cs.tcd.ie>
To: public-multilingualweb-lt@w3.org
Hi Felix,
Talking in terms of files or content item specifically makes sense in 
the technical specification. However in the requirements document, 
referencing the actual product classes, such as CMS, rather than just 
talking more abstractly about files, would resonate more clearly with 
readers of a use case or requirement who is trying to understand the 
benefit it might have for them.

So I'd be against such a blanket change since if we only talk in terms 
file formats it will be more difficult to many readers to map that into 
actual problems.

cheers,
Dave


On 16/05/2012 20:09, MultilingualWeb-LT Working Group Issue Tracker wrote:
> mlw-lt-track-ISSUE-21 (cms-related-terminology): CMS related terminology: not only CMS as content [MLW-LT Requirements Document]
>
> http://www.w3.org/International/multilingualweb/lt/track/issues/21
>
> Raised by: Felix Sasaki
> On product: MLW-LT Requirements Document
>
> In many areas, the requirements document puts CMS in the centre, e.g. in the use case "CMS-Side Revision Management". I propose that rather we talk about content, that may be available in a CMS, an XML file or from other pieces of content. If we agree on this, an action item is needed to go through the whole document and change the terminology.
>
>
>
Received on Thursday, 17 May 2012 11:07:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:31:44 UTC