{"id":48,"date":"2016-05-20T13:04:22","date_gmt":"2016-05-20T13:04:22","guid":{"rendered":"http:\/\/habett.fr\/blog\/?p=48"},"modified":"2016-07-23T09:20:38","modified_gmt":"2016-07-23T09:20:38","slug":"google-license-to-forget","status":"publish","type":"post","link":"https:\/\/habett.fr\/blog\/2016\/05\/google-license-to-forget\/","title":{"rendered":"Google: license to forget ?"},"content":{"rendered":"<p>Je publie de la musique sous licence creative commons sur un de mes sites (<a href=\"http:\/\/habett.net\">http:\/\/habett.net<\/a>). L&rsquo;ayant refait il y a quelques mois, je me suis pos\u00e9 des questions quant \u00e0 l&rsquo;exposition et la coh\u00e9rence du balisage des mes m\u00e9tadonn\u00e9es et j&rsquo;ai fini par m&rsquo;orienter essentiellement vers la technologie json-ld.<\/p>\n<p>Je mets en place mes donn\u00e9es et m\u00e9tas et apr\u00e8s quelques t\u00e2tonnements je finis par obtenir la validation par l&rsquo;outil google de test des donn\u00e9es structur\u00e9es (<a href=\"https:\/\/search.google.com\/structured-data\/testing-tool\/u\/0\/\">https:\/\/search.google.com\/structured-data\/testing-tool\/u\/0\/<\/a>). Je suis content. Je retourne il y a quelques jours pour v\u00e9rifier un truc et je constate que mon json-ld est maintenant marqu\u00e9 comme contenant des erreurs. Je ne suis plus content. Je v\u00e9rifie avec schema.org que j&rsquo;utilise pour mes d\u00e9finitions et je constate que mes structures semblent encore correctes. Voici un exemple minimal:<\/p>\n<blockquote>\n<pre>{\r\n \"@context\" : \"<a href=\"http:\/\/schema.org\">http:\/\/schema.org<\/a>\",\r\n \"@type\" : \"CreativeWork\",\r\n \"name\" : \"DJ Habett\",\r\n \"alternateName\" : \"Free music for unfree people\",\r\n \"url\" : \"<a href=\"http:\/\/habett.net\">http:\/\/habett.net<\/a>\",\r\n \"license\": \"<a href=\"http:\/\/creativecommons.org\/licenses\/by-sa\/3.0\/fr\/\">http:\/\/creativecommons.org\/licenses\/by-sa\/3.0\/fr\/<\/a>\"\r\n }<\/pre>\n<\/blockquote>\n<p>C&rsquo;est tr\u00e8s simple \u00e0 priori, un travail cr\u00e9atif auquel on rattache une licence d\u00e9sign\u00e9e par son URL. (<a href=\"https:\/\/schema.org\/CreativeWork\">https:\/\/schema.org\/CreativeWork<\/a>) et (<a href=\"https:\/\/schema.org\/license\">https:\/\/schema.org\/license<\/a>). L&rsquo;outil google r\u00e9pond (alors qu&rsquo;il n&rsquo;y trouvait rien \u00e0 redire il y a quelques semaines):<\/p>\n<blockquote><p>\u00ab\u00a0Nous ne reconnaissons pas la propri\u00e9t\u00e9\u00a0<i>http:\/\/www.w3.org\/1999\/xhtml\/vocab#license\u00a0<\/i>pour un objet de type\u00a0<i>CreativeWork<\/i>.\u00a0\u00bb<\/p><\/blockquote>\n<p>Selon moi la propri\u00e9t\u00e9 \u00ab\u00a0license\u00a0\u00bb est connue (cf schema.org) mais par google \u00ab\u00a0plus reconnue\u00a0\u00bb et non pas \u00ab\u00a0pas reconnue\u00a0\u00bb car cela fonctionnait encore r\u00e9cemment.<\/p>\n<p>Que dire ? Je ne vais pas \u00eatre le seul (<a href=\"http:\/\/stackoverflow.com\/questions\/35844485\/mixing-json-ld-and-microdata-schema-org\">http:\/\/stackoverflow.com\/questions\/35844485\/mixing-json-ld-and-microdata-schema-org<\/a>) (impact entre 1000 et 10000 domaines selon schema.org).<\/p>\n<p>Nihilisme ou r\u00e9visionnisme ?<\/p>\n<p>(<a href=\"https:\/\/productforums.google.com\/forum\/?utm_medium=email&amp;utm_source=footer#!msg\/webmasters\/yPcF6rteIqo\/ZlhapEEVBQAJ\">https:\/\/productforums.google.com\/forum\/?utm_medium=email&amp;utm_source=footer#!msg\/webmasters\/yPcF6rteIqo\/ZlhapEEVBQAJ<\/a>)<\/p>\n<p>PS: J&rsquo;ai signal\u00e9 l&rsquo;erreur en utilisant l&rsquo;outil google d\u00e9di\u00e9 mais pas de r\u00e9ponse pour le moment.<\/p>\n<p>PS: R\u00e9par\u00e9 par google d\u00e9but juillet.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Je publie de la musique sous licence creative commons sur un de mes sites (http:\/\/habett.net). L&rsquo;ayant refait il y a quelques mois, je me suis pos\u00e9 des questions quant \u00e0 l&rsquo;exposition et la coh\u00e9rence du balisage des mes m\u00e9tadonn\u00e9es et j&rsquo;ai fini par m&rsquo;orienter essentiellement vers la technologie json-ld. Je mets en place mes donn\u00e9es &hellip; <a href=\"https:\/\/habett.fr\/blog\/2016\/05\/google-license-to-forget\/\" class=\"more-link\">Continuer la lecture de <span class=\"screen-reader-text\">Google: license to forget ?<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[15,17,7,16],"class_list":["post-48","post","type-post","status-publish","format-standard","hentry","category-non-classe","tag-creative-commons","tag-json-ld","tag-metadata","tag-rights"],"_links":{"self":[{"href":"https:\/\/habett.fr\/blog\/wp-json\/wp\/v2\/posts\/48","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/habett.fr\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/habett.fr\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/habett.fr\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/habett.fr\/blog\/wp-json\/wp\/v2\/comments?post=48"}],"version-history":[{"count":9,"href":"https:\/\/habett.fr\/blog\/wp-json\/wp\/v2\/posts\/48\/revisions"}],"predecessor-version":[{"id":58,"href":"https:\/\/habett.fr\/blog\/wp-json\/wp\/v2\/posts\/48\/revisions\/58"}],"wp:attachment":[{"href":"https:\/\/habett.fr\/blog\/wp-json\/wp\/v2\/media?parent=48"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/habett.fr\/blog\/wp-json\/wp\/v2\/categories?post=48"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/habett.fr\/blog\/wp-json\/wp\/v2\/tags?post=48"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}