Re: ITS 2.0 Logo

Hi,

I think someone had this idea already. The Problem I see here, with 20 
different data categories it will be a very big logo.

I like the idea from Felix better to just say "10 
inside/included/supported". For more information you can read the 
documentation.

On the other hand, if we would have such logos for each data category, 
these could also be used in the implementation. Like in our case to use 
these as buttons for the WYSIWYG editor or in other implementations to 
add these as example in menus. Would be a great recognition value across 
all implementation. But I'm not sure in how many other implementations 
you would have a use for these.

Cheers
Karl

On 25.04.2013 15:50, Lieske, Christian wrote:
>
> Hi,
>
> Talking about a logo that reveals information about capabilities 
> (conformance types in ITS 2.0 
> http://www.w3.org/TR/its20/#conformance), we possibly can inform 
> ourselves by
>
> Source: http://www.w3.org/html/logo/
>
> Cheers,
>
> Christian
>
> *From:*Felix Sasaki [mailto:fsasaki@w3.org]
> *Sent:* Donnerstag, 25. April 2013 15:03
> *To:* Dr. David Filip
> *Cc:* "Pedro L. Díez Orzas"; public-multilingualweb-lt@w3.org
> *Subject:* Re: ITS 2.0 Logo
>
> You are touching an important point, David.
>
> "Supporting ITS 2.0" is a much too general statement. For that reason 
> we have a conformance section. Implementations being advertised to the 
> outside or being adequately documented should always make clear:
>
> - these are the data categories implemented
> - these are global / local functionalities
> - these are HTML / XML processing
>
> Now, about the number of logos ... in other technical areas there are 
> also slogans like "xxx inside!" to express that a certain CPU is used. 
> No details about the CPU capabilities, variants etc. are being 
> expressed. And 19 data categories = 19 logos also probably won't fly?
>
> Best,
>
> Felix
>
> Am 25.04.13 14:44, schrieb Dr. David Filip:
>
>     Thanks Pedro, for summarizing the options.
>
>     I see marketing advantages of having only one logo, but also
>     technical disadvantages (that can in longer term turn into
>     marketing disadvantages) of the one logo approach.
>
>     With 20 independent data categories, the one badge is a hopelessly
>     vague statement. And hence I believe the technical disadvantage of
>     not being able to visibly state specific categories support will
>     render the one logo practically useless as a product/page badge.
>
>     About 2 or 3. It is rather vague, in what sense the logo should be
>     dependent or independent.
>
>     In my view it should be dependent in terms of the color palette
>     and typography, but should only contain ITS 2.0 in prominent large
>     type.
>
>     A larger version can contain a lemma similar to the one proposed
>     by Pedro stating affinity or affiliation with the MultilingualWeb
>     brand.
>
>     Cheers
>
>     dF
>
>
>     Dr. David Filip
>
>     =======================
>
>     LRC | CNGL | LT-Web | CSIS
>
>     University of Limerick, Ireland
>
>     telephone: +353-6120-2781
>
>     *cellphone: +353-86-0222-158*
>
>     facsimile: +353-6120-2734
>
>     mailto: david.filip@ul.ie <mailto:david.filip@ul.ie>
>
>     On Wed, Apr 24, 2013 at 2:23 PM, Pedro L. Díez Orzas
>     <pedro.diez@linguaserve.com <mailto:pedro.diez@linguaserve.com>>
>     wrote:
>
>     Dear all,
>
>     Dear all,
>
>     In the call today was decided to open the discussion about
>     creating a logo for ITS 2.0. This logo could be used in the
>     websites that incorporate ITS 2.0 recommendation or in ITS 2.0
>     compliant applications
>
>     I will try to summarize. For the moment there are 3 approaches,
>     but probably we should check with Richard how recommendation logos
>     are usually treated in the W3C?:
>
>     1)To create a logo for all the 20 data categories and for the ITS
>     2.0 standard
>
>     a.Since it is rare somebody use all data categories, they could
>     identified which ones are used, together with the ITS 2.0 logo.
>
>     2)To create only one ITS logo, *based on the MLW logo* (like we
>     based the MLW-LT logo on the MLW logo). Benefits:
>
>     a.The MLW logo is known already, so people will recognize
>     something familiar.
>
>     b.The story "makes sense": ITS is one piece of technologies that
>     fosters the adoption of the Multilingual Web
>
>     c.Using the MLW+ITS logo in user interfaces would be one part of a
>     sustainable story for both MLW and ITS, since the user interfaces
>     will for sure stay alive after the end of LT-Web.
>
>     3)To create only one ITS logo, different and independent from MLW
>     logo.
>
>     At this point, my view is:
>
>     a)The idea for one logo for ITS 2.0 is good. It gives visibility
>     to the recommendation and allows to "sell" it better. Also, we
>     need to have very clear that key of success of ITS 2.0 is that
>     content creators use it!
>
>     b)IMHO it is better to promote only one ITS 2.0 good logo, to be
>     used in web, rather than 20 data categories logos. From commercial
>     perspective it is better to have a good well known logo than 20.
>
>     c)We could try to make compatible option 2 and 3, with "some"
>     relation to MLW, but not the same logo.
>
>     My very humble proposals (just to start discussing and to be
>     discarded -- I am not graphic creative guy) are simple. The
>     relation with MLW are colors and the lemma in the second one:
>
>     Any thought or proposal?
>
>     Best,
>
>     Pedro
>
>     *_________________________________*
>
>     **
>
>     *Pedro L. Díez Orzas*
>
>     *Presidente Ejecutivo/CEO*
>
>     *Linguaserve Internacionalización de Servicios, S.A.*
>
>     *Tel.: +34 91 761 64 60 <tel:%2B34%2091%20761%2064%2060>
>     Fax: +34 91 542 89 28 <tel:%2B34%2091%20542%2089%2028> *
>
>     *E-mail: **pedro.diez@linguaserve.com
>     <mailto:pedro.diez@linguaserve.com>*
>
>     *www.linguaserve.com <http://www.linguaserve.com/>*
>
>     **
>
>     «En cumplimiento con lo previsto con los artículos 21 y 22 de la
>     Ley 34/2002, de 11 de julio, de Servicios de la Sociedad de
>     Información y Comercio Electrónico, le informamos que procederemos
>     al archivo y tratamiento de sus datos exclusivamente con fines de
>     promoción de los productos y servicios ofrecidos por LINGUASERVE
>     INTERNACIONALIZACIÓN DE SERVICIOS, S.A. En caso de que Vdes. no
>     deseen que procedamos al archivo y tratamiento de los datos
>     proporcionados, o no deseen recibir comunicaciones comerciales
>     sobre los productos y servicios ofrecidos, comuníquenoslo a
>     clients@linguaserve.com <mailto:clients@linguaserve.com>, y su
>     petición será inmediatamente cumplida.»
>
>     "According to the provisions set forth in articles 21 and 22 of
>     Law 34/2002 of July 11 regarding Information Society and eCommerce
>     Services, we will store and use your personal data with the sole
>     purpose of marketing the products and services offered by
>     LINGUASERVE INTERNACIONALIZACIÓN DE SERVICIOS, S.A. If you do not
>     wish your personal data to be stored and handled, or you do not
>     wish to receive further information regarding products and
>     services offered by our company, please e-mail us to
>     clients@linguaserve.com <mailto:clients@linguaserve.com>. Your
>     request will be processed immediately."
>
>     *____________________________________*
>


-- 
*Karl Fritsche*, Software Developer
Tel.: +49 69 972 69 2604; Mob.: +49 1520 206 30 93; Fax: +49 69 972 69 
199; Email: Karl.Fritsche@cocomore.com <mailto:karl.fritsche@cocomore.com>
*Cocomore AG,* Gutleutstraße 30, D-60329 Frankfurt
Internet: http://www.cocomore.de <http://www.cocomore.de/> Facebook: 
http://www.facebook.com/cocomore Google+: http://plus.cocomore.de 
<http://plus.cocomore.de/>
Cocomore is active member of the World Wide Web Consortium (W3C)
Vorstand: Dr. Hans-Ulrich von Freyberg (Vors.), Dr. Jens Fricke, Marc 
Kutschera, Vors. des Aufsichtsrates: Martin Velasco, Sitz: 
Frankfurt/Main, Amtsgericht Frankfurt am Main, HRB 51114

Received on Thursday, 25 April 2013 15:21:01 UTC