Recherche avancée

Sur d’autres sites (8266)

• Why I became a HTML5 co-editor

  1er janvier 2014, par silvia

  A few weeks ago, I had the honor to be appointed as part of the editorial team of the W3C HTML5 specification.

  Since Ian Hickson had recently decided to focus solely on editing the WHATWG HTML living standard specification, the W3C started looking for other editors to take the existing HTML5 specification to REC level. REC level is what other standards organizations call a “ratified standard”.

  But what does REC level really mean for HTML ?

  In my probably somewhat subjective view, recommendation level means that a snapshot is taken of the continuously evolving HTML spec, which has a comprehensive feature set, that is implemented in a cross-browser interoperable way, has a complete test set for the features, and has received wide review. The latter implies that other groups in the W3C have had a chance to look at the specification and make sure it satisfies their basic requirements, which include e.g. applicability to all users (accessibility, internationalization), platforms, and devices (mobile, TV).

  Basically it means that we stop for a “moment”, take a deep breath, polish the feature set that we’ve been working on this far, and make sure we all agree on it, before we get back to changing the world with cool new stuff. In a software project we would call it a release branch with feature freeze.

  Now, as productive as that may sound for software – it’s not actually that exciting for a specification. Firstly, the most exciting things happen when writing new features. Secondly, development of browsers doesn’t just magically stop to get the release (REC) happening. And lastly, if we’ve done our specification work well, there should be only little work to do. Basically, it’s the unthankful work of tidying up that we’re looking at here.

  So, why am I doing it ? I am not doing this for money – I’m currently part-time contracting to Google’s accessibility team working on video accessibility and this editor work is not covered by my contract. It wasn’t possible to reconcile polishing work on a specification with the goals of my contract, which include pushing new accessibility features forward. Therefore, when invited, I decided to offer my spare time to the W3C.

  I’m giving this time under the condition that I’d only be looking at accessibility and video related sections. This is where my interest and expertise lie, and where I’m passionate to get things right. I want to make sure that we create accessibility features that will be implemented and that we polish existing video features. I want to make sure we don’t digress from implementations which continue to get updated and may follow the WHATWG spec or HTML.next or other needs.

  I am not yet completely sure what the editorship will entail. Will we look at tests, too ? Will we get involved in HTML.next ? This far we’ve been preparing for our work by setting up adequate version control repositories, building a spec creation process, discussing how to bridge to the WHATWG commits, and analysing the long list of bugs to see how to cope with them. There’s plenty of actual text editing work ahead and the team is shaping up well ! I look forward to the new experiences.

• Why I became a HTML5 co-editor

  15 août 2012, par silvia

  A few weeks ago, I had the honor to be appointed as part of the editorial team of the W3C HTML5 specification.

  Since Ian Hickson had recently decided to focus solely on editing the WHATWG HTML living standard specification, the W3C started looking for other editors to take the existing HTML5 specification to REC level. REC level is what other standards organizations call a “ratified standard”.

  But what does REC level really mean for HTML ?

  In my probably somewhat subjective view, recommendation level means that a snapshot is taken of the continuously evolving HTML spec, which has a comprehensive feature set, that is implemented in a cross-browser interoperable way, has a complete test set for the features, and has received wide review. The latter implies that other groups in the W3C have had a chance to look at the specification and make sure it satisfies their basic requirements, which include e.g. applicability to all users (accessibility, internationalization), platforms, and devices (mobile, TV).

  Basically it means that we stop for a “moment”, take a deep breath, polish the feature set that we’ve been working on this far, and make sure we all agree on it, before we get back to changing the world with cool new stuff. In a software project we would call it a release branch with feature freeze.

  Now, as productive as that may sound for software – it’s not actually that exciting for a specification. Firstly, the most exciting things happen when writing new features. Secondly, development of browsers doesn’t just magically stop to get the release (REC) happening. And lastly, if we’ve done our specification work well, there should be only little work to do. Basically, it’s the unthankful work of tidying up that we’re looking at here.

  So, why am I doing it ? I am not doing this for money – I’m currently part-time contracting to Google’s accessibility team working on video accessibility and this editor work is not covered by my contract. It wasn’t possible to reconcile polishing work on a specification with the goals of my contract, which include pushing new accessibility features forward. Therefore, when invited, I decided to offer my spare time to the W3C.

  I’m giving this time under the condition that I’d only be looking at accessibility and video related sections. This is where my interest and expertise lie, and where I’m passionate to get things right. I want to make sure that we create accessibility features that will be implemented and that we polish existing video features. I want to make sure we don’t digress from implementations which continue to get updated and may follow the WHATWG spec or HTML.next or other needs.

  I am not yet completely sure what the editorship will entail. Will we look at tests, too ? Will we get involved in HTML.next ? This far we’ve been preparing for our work by setting up adequate version control repositories, building a spec creation process, discussing how to bridge to the WHATWG commits, and analysing the long list of bugs to see how to cope with them. There’s plenty of actual text editing work ahead and the team is shaping up well ! I look forward to the new experiences.

• Powerful Video Analytics and Audio Analytics for Piwik

  10 novembre 2016, par InnoCraft — Plugins, Press Releases

  Over the years, one of the most frequently requested feature by users was to be able to measure how videos and audios are watched and engaged with on your website. We are finally able to announce that it is here ! We are very excited to launch Media Analytics, which will help you understand and grow your audience.

  This article is a showcase of the new powerful video and audio analytics product built for Piwik.

  Why media analytics ?

  We all love media content such as videos as they can make our experiences on websites and apps so much more interesting. A growing number of websites now utilize media files in one form or another : a video presentation of a product or service, a video tutorial teaching you how to do something or interviews with key speakers. Also many creators and distributors are publishing audio files such as podcasts or music songs, and even broadcasting live video events such as music concerts or an entire conference online.

  Whenever you publish videos or audio media on your websites or applications, Media Analytics provides you with clear insights on how your audience interacts with your content. It helps you see what content works and why – so you can better understand and further grow your business !

  

  Valuable insights in Real time

  

  See where your audience comes from.

  How will Media Analytics help me grow ?

  • Better understand your audience : who are the users playing videos and for how long, how often, and where have they dropped off.
  • Gain quick insights into how interaction with your media changes over time with easy to use graphs and report overviews.
  • Get closer to your users by seeing every action of your visitors before and after they utilized your media.
  • View valuable insights in Real time : ‘most popular content right now’, your real time audience map, and more.
  • See where your audience comes from. Drill down right from continents to specifics such as cities.
  • Share and export media analytics reports with your colleagues by creating custom email reports.
  • Video and audio players are supported either automatically (for Youtube, Vimeo, HTML5…) or via a simple custom player integration.
  • No data limit and 100% privacy and data ownership.

  Best of all, it is easy to use and understand, and integrates perfectly with Piwik. Media Analytics complements other reports to give you a 360 degree view of how your users engage with your content.

  Learn more on the official website : www.media-analytics.net

  How do I get Media Analytics ?

  All premium plugins come with our 14 day money back guarantee and 1-click installation & updates. Customers get all product updates for free.

  Learn more about Media Analytics Get it now on the Marketplace

  Media Analytics is available for purchase and download on the Marketplace.

  If you are not using Piwik yet, you can also signup for a free trial of Piwik Cloud (including Media Analytics !).

  Have a question about this product ? Get in touch.