<Ashok> What is the conference code?

75464

MAWG feedback

http://lists.w3.org/Archives/Public/public-pling/2010Apr/0010.html

RI comments

http://lists.w3.org/Archives/Public/public-pling/2010Apr/0011.html

Other ideas?

Policy types?

DavidC: Sticky policies from PrimeLife - list of policy types

Hannes: keep it simple

DC: policy language specified?

Hannes: see CC as example, loose binding to content

<tlr> tlr: recommend simplifying

<tlr> ... identifier (URI)

<tlr> ... type (URI)

<tlr> ... that's all

<tlr> ... propose dropping value, organization

Thomas: Identifier - maybe deref or just the "identifier"

DavidC: need to get the policy?

<tlr> http://www.w3.org/Submission/ccREL/

<tlr> the point is: identifier is an *identifier*

<tlr> http://lists.w3.org/Archives/Public/public-pling/2010Apr/0010.html

"This attribute holds the description of the license"

<tlr> http://www.w3.org/1999/xhtml/vocab/#

policy.type: see RDFa

<tlr> license

<tlr> license refers to a resource that defines the associated license.

http://www.w3.org/TR/mediaont-10/#property-definition

ma: copyright = The copyright statement. Identification of the copyrights holder (Digital Right Management is out of scope for MAWG, see the [PLING] for more information on this topic
... policy = Description of the policy of the media resource or reference. see the [PLING] for more information on this topic

<tlr> I'm actually becoming convinced of having a policy field with a human-readable attribute, and http://www.w3.org/1999/xhtml#license as the canonical type for a copyright license.

So if you look at:

http://lists.w3.org/Archives/Public/public-pling/2010Apr/0011.html

and remove "issuer"

are were there?

<tlr> wfm

ma: createDate

<tlr> also, make type URI-valued

yes

use the xhtml license URI

<scribe> ACTION: RI to writeup updated proposal for MAWG and sent to list [recorded in http://www.w3.org/2010/05/11-pling-minutes.html#action01]

<spreibus> apologies for the late arrival -- I only got the message about the time shift to 12h UTC now.

OK - thanks for joining!

<scribe> Agenda: US Privacy Bill

http://www.boucher.house.gov/images/stories/Privacy_Draft_5-10.pdf

<spreibus> Thanks.

<tlr> http://www.ntia.doc.gov/frnotices/2010/FR_PrivacyNOI_04232010.pdf

Update on Current Items

PLING note....still going....contributions welcome

Geolocation Privacy

Workshop planned

<spreibus> re PLING note on Best Practices:

<tlr> http://www.w3.org/2010/api-privacy-ws/

<spreibus> how much of the "User Consent" is happening in the user agent and how much through the site? I would argue the browser is the better place, mainly because (a) it allows consistent presentation, similar to the current information bar in browsers, e.g. Firefox for GeoLocation; (b) because it allows recording of consent, similar to stored passwords

<tlr> spreibus, a possible answer is that access control isn't privacy

<tlr> we know how to do access control in the browser.

<spreibus> true, access control is not privacy.

<spreibus> I see the best practices as reaching beyond access.

<spreibus> eventually emphasising "informed consent"

Thomas, can u make the minutes and make public?

This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: renato
Inferring Scribes: renato

WARNING: No "Topic:" lines found.

Default Present: +352.6.2.1.5.0.aaaa, +035850487aabb, Ashok_Malhotra, Thomas
Present: +352.6.2.1.5.0.aaaa +035850487aabb Ashok_Malhotra Thomas

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 11 May 2010
Guessing minutes URL: http://www.w3.org/2010/05/11-pling-minutes.html
People with action items: ri

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report