Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

...

...

...

...

...

Information Sharing Work Group Teleconference

Table of Contents
maxLevel3
minLevel3
typeflat
separatorpipe

Date and Time

  • Tuesday, Sep 24 : 9am Oct 1 : 4:30pm PDT, 12pm 7:30pm EDT
  • Wednesday, Sep 25 : 5pm Oct 2 : 12:30am UK, 1am 8:30am JT, 4am 12pm NZDT  

  • Please join  my meeting  via GoToMeeting
  • Join the conference call
    • Skype: +99051000000481
    • US Dial-In: +1-805-309-2350
    • UK Dial-In: +44-20-3137-5285
    • Conference ID: 178-2540
    • GoToMeeting ID: 844-771-298

Attendees

  • Joe Andrieu
  • LIonel Klee

Apologies

Agenda

  1. Attendance
  2. Approval of Prior Minutes & Other Motions
  3. Prior Action Item Review
  4. Continuing Business
    1. Rechartering
    2. Open Notice
  5. New Business
  6. Action Item Review
  7. Next meeting schedule

Minutes

1. Attendance

We noted that with 2 of 5 8 voting members in attendance, quorum was not met. 

2. Motions

None

3. Prior Action Item Review

4. Continuing Business

Rechartering

Need input from Mark, Par and Nick.

Revisions

 No discussion

 

5. New Business

Open Notice

Added some pages to Open Notice with some discussions and feedback on the initial round of conversations on the list. A few example use cases: simple, value added transactions–just the title!  Also a sandbox for schema (we added Joe's input from the email), and a Schema Requirements discussion page to try to get consensus on the larger needs before we dive into a serialized format.

Agreed that we need to both paint the bigger, longer term picture of what we are trying to build AND execute the first, simplest specification toward that.

 Reviewed charter. Updated a bit. Will send out a call for objections. If anyone objects, we'll call for a formal evote.

Redesign

Looking at how to shorten the label, continuing in part from Weekly Meeting 2013 08 06 Notes. We looked at traffic light labeling in the UK to see if we can leverage any of that. One challenge: a light might stand in judgment, e.g., as http://tosdr.org/ does.

Talked about Amazon needs for one-click purchases and also merchants who have a single page check out, where different info in the form is 

 

  1. Seen and checked and thrown away, e.g, CVV or Credit Card #s, depending on vendor
  2. Stored briefly for transaction/use 
  3. Logged for transaction (indefinite)
  4. Retained for active use (indefinite)

Let's build on what we've already done: http://kantarainitiative.org/confluence/download/attachments/58493242/ISWG+Standard+Information+Sharing+Label.Draft+Report.v.0.4.pdf?version=1&modificationDate=1343922915000

One that's missing is the difference between logs and retained for active use.

Should the label identify what is used for business operations verses IT administration

The label gets crazy if we are also adding in details about IP addresses, cookies, refererers, etc.

But maybe there is a label for that. For a website. The default label. Not specific to a web form or data transaction, but specific to IP addresses. What do they do with just an HTTP request.

What happens when you have 75 cookies and beacons on a single page? 

You should be able to see the label for every cookie.

 

 

5. New Business

none

 6. Action Items

None.

 

7. Next Meeting

  • Tuesday  September 10  October 8 : 9:00 am PDT, 12:00pm EDT,  5:00pm UK,
  • Wednesday September 11 October 9 2:00am JT, 5:00am NZT
  • 60 minutes