...
- we discuss the json being a part of the main MVCR.
- John YesNo - should go in to appendix
- Mark No Yes - its not that simple.. partially yes, we can seprate it , but difinively no to moving to out of spec into appendix
- Mary Yes
- like the logic of having the JSN filelds makes sens in opening technical side or use, at least as example
- good to take time and ask opinions of people with experience
- Mary - what would the questions be to others? how do we involve others?
- should the consent receipt be a policy format agnostic to any format like JSON
- Mary - what would the questions be to others? how do we involve others?
- should the consent receipt have a framework as a suggestion, recommened with caveat that any others can be made.
- What examples should we look at ?
- calendar
- mac, yahoo, msft
- calendar
- What examples should we look at ?
- micro formats
- Pop-SMTP
- Do Not Track
- Ad-Blocker
- Cookie implementations
- number of instances in the existing formats - how (in what way) to pick what micros format for the fields -
- bottom up is the date and time example
- suggests looking at five.
- bottom up is the date and time example
- Iain
- marketers want a spec - and common standard. No competitors to this yet, we need to get it out.
- - as long as it delivers a minimum viable policy for implementation - lets get it done
- ineeds an output simple marketing language
- needs to be able to be used as a marketing tool. (business requirements)
- (everyone agree's)
- Mary - Brought up Uber as interested in the consent receipt and UST
- may be able to get implementaton wth them
- Mark Suggest that spec can have the guidance for the policy of putting a receipt in any format or a single format be open, (and still be compliant with MVCR spec) while also, using a common JSON format for example and development of v.1 - (as apart of main spec) for help with implementation and , needed to make MVCR useful for inter-op. (which is a key priority)
- asking can this can be done via a table in main spec as (default example)
- we ta tabled this issue for github and asking advice
- going forward- general proposal
- use call time to go through fields and write spec to consensus. (5 min max to discuss item/5 min to write item as issue)
- if we have an issue or discussion item, (5 min to record it/5 to discuss it )
- (notes)
- Try to bring issues you might have for the spec up on the list before the call so that we can have best chance of dealing with issues in consensus on the call
- all items that people need time on can be tabled for one week. (upon request)
- (notes)
- if we have an issue or discussion item, (5 min to record it/5 to discuss it )
- use call time to go through fields and write spec to consensus. (5 min max to discuss item/5 min to write item as issue)
...