See also: IRC log
-> https://lists.w3.org/Archives/Public/public-web-and-tv/2016Mar/0006.html
glennd: discussion on
identity
... future web standards for entertainment industry
... content identifier we discussed last year
... we had discovered three ways
... 1. extract from meta data
... 2. attract with fingerprinting watermark
... id work
... api for content identifier
... any other points?
julian: sounds good
glennd: very future one or near
future one
... what we're doing is very important
kaz: we might want to mention the
structure of use case wiki
... including the recent work on identifier management
discussion
bill: deadline?
glennd: Mark didn't mention that
bill: what we're doing is
entertainment in general
... maybe we can point our use case wikis
glennd: anybody can do discussion on the reflector
bill: sounds like a good idea
glennd: take an action
<scribe> ACTION: glenn to send out an initial idea to the GGIE reflector on future web standard [recorded in http://www.w3.org/2016/03/09-webtv-minutes.html#action01]
<trackbot> 'glenn' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., gadams, gdeen, geguchi, ggoldste).
-> https://github.com/w3c/tv-ggie/blob/master/GGIE.Identity.UC.Requirements.md ID UC/Req. doc on GitHub
glennd: second point is
requirements document, third point is privacy
... any other items?
(none)
glennd: number of action
items
... would go through the github doc
... the first topic is "Privacy Requirements"
<scribe> ACTION: glennd to update the numbering of the github doc [recorded in http://www.w3.org/2016/03/09-webtv-minutes.html#action02]
<trackbot> Created ACTION-216 - Update the numbering of the github doc [on Glenn Deen - due 2016-03-16].
glennd: many requirements
julian: unique ID code to identify students?
bill: could be unique within
organization, etc.
... but might want to have a third party to manage a global
ID
... separation from your real identity
julian: so the name of the student and the token are both publicly available?
bill: the exchange might be encrypted
glennd: functional aspect of
identity
... not how to authenticate
bill: the idea is e.g., online
shopping
... it's a MAY
glennd: may take preamble?
bill: preamble of the requirement
document?
... will do
... where they came from
... number of requirements documents
leslie: having a link would be
helpful
... a bit concerned with the ordering
glennd: suggesting to use
linking?
... let's do use cases by name
kaz: mentions the work of the TV Control API CG
-> https://www.w3.org/2016/03/08-tvapi-minutes.html TV Control API CG minutes (including several resources on security)
glennd: we've identified
preamble
... updated the github doc
... Ease of Use Requirements
bill: more a guideline
glennd: number 1: The methods
necessary to achieve anonymity and pseudonymity must be simple
to understand and use such as, for example, the methods used
for parental control of online access for children today.
... very general
... next: Issuer Requirements
... user driven
... propagation ok
... Import/Export Requirements
... Processor/Workflow Requirements
bill: we had an action item
glennd: action item for us
<scribe> ACTION: bill and glennd to flesh out the Processor/Workflow requirements section [recorded in http://www.w3.org/2016/03/09-webtv-minutes.html#action03]
<trackbot> 'bill' is an ambiguous username. Please try a different identifier, such as family name or username (e.g., wdh, WJR).
glennd: any issues on Device Requirements or Business Requirements?
bill: security requirements
glennd: good catch
... updated the github doc
... plan to send this note out to the GG list to request review
of the larger group
... any comments?
(none)
glennd: general privacy
document
... use case we did last year concerning EPG, etc.
... number of sections we had identified
... starting point suggestions
... go back through the use cases and identify gaps
... capture them at one place
julian: sounds like reasonable
(everybody is OK)
glennd: julian and bill, would like to do?
julian: happy to help
bill: signs up
glennd: the first pass is where
the use cases came from
... natural aggregation
bill: also would see privacy requirements
glennd: discovery stuff as well potentially
bill: being informative
glennd: any other comments?
(none)
glennd: the other stage we might
want to spend time is content identification requirements
... previously discussed what APIs for content
identification
... would do a document
... potentially related to some other work within W3C
[ adjourned ]