Scope clarification for guidelines

[joelkorpi]

After talking with @thasso today at the F2F, we propose that we should clearly define and limit the scope of v1 of the guidelines to not include superfluous content. I propose that, for example, we NOT include full player implementation examples with code samples and configurations, but rather we discuss overall guidelines for implementations and link to specific technology implementation guidelines (such as JW Player, etc.).

[andybeach]

i noticed the guidelines are missing CC/subtitles. there will be a lot of requests for clarification on accessibility in the initial draft.

[joelkorpi]

@andybeach Great point Andy. I think we should track this as it's own issue as it's very important. Would you mind posting a new issue that we can track this under? I'll make sure it's also included in the scope.

[thasso]

I agree with @joelkorpi that keep the first iteration short and focus on the main issues.

[andybeach]

Will do

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Joel Korpi notifications@github.com Sent: Thursday, May 4, 2017 8:08:14 AM To: w3c/webmediaguidelines Cc: Andy Beach; Mention Subject: Re: [w3c/webmediaguidelines] Scope clarification for guidelines (#5)

@andybeachhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fandybeach&data=02%7C01%7CAndy.Beach%40microsoft.com%7Cce392663cedf45e2dbd408d492ff64e7%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636295073043250430&sdata=4ASTRVGqMRg6fx0A36kbn7rQncNY%2FPMeALs34dk%2FWTI%3D&reserved=0 Great point Andy. I think we should track this as it's own issue as it's very important. Would you mind posting a new issue that we can track this under? I'll make sure it's also included in the scope.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwebmediaguidelines%2Fissues%2F5%23issuecomment-299213908&data=02%7C01%7CAndy.Beach%40microsoft.com%7Cce392663cedf45e2dbd408d492ff64e7%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636295073043250430&sdata=eo0%2BHPXmIJYvKdk1x4V3ptkhADbUPddaigqCjgJ8yi8%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJrY1CQi_wOAUExVadgv4nCccDFUsJ5zks5r2enegaJpZM4NK1-W&data=02%7C01%7CAndy.Beach%40microsoft.com%7Cce392663cedf45e2dbd408d492ff64e7%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636295073043250430&sdata=qXLJlGhjm1%2F4m3Zg8iv3dkwSAQ2LW%2FYmybZgAzf3ZCk%3D&reserved=0.

[joelkorpi]

Also, as discussed on the weekly call yesterday, in regards to code examples, sample players, and all additional samples: All examples we link to will be stored in a repository that we can link to and also clone and host (within CTA/W3C) if we choose.

[joelkorpi]

Proposed scope definition is below. Please comment on any changes @thasso @boyofgreen

The scope of this document includes general guidelines, best practices, and examples for building media applications across web browsers and devices. This includes native and browser-based applications as well as integrated and stand-alone devices. The examples in this document provides a starting point to build your media application and includes example implementations from various providers and vendors. This document also includes sample content and manifests as well as encoding guidelines to maximize the provide hints on achieving the best quality and efficiency for your media applications.

[joelkorpi]

Additional notes from @mavgit "I've always assumed that while WAVE overall applies to both HTML and non-HTML apps (e.g. the content spec) , the two WAVE HATF specs are of limited application to only HTML apps and have no applicability to non-HTML apps."

[joelkorpi]

Issue has been closed