Weekly Meeting 2013 10 15 Notes

Owned by Former user (Deleted)
Last updated: Oct 15, 2013Version comment

Information Sharing Work Group Teleconference

Date and Time

  • Tuesday, Oct 15 : 4:30pm PDT, 7:30pm EDT
  • Wednesday, Oct 16 : 12:30am UK, 8:30am JT, 12pm NZDT  
  • 60 minutes 

  • 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 8 voting members in attendance, quorum was not met. 

2. Motions

None

3. Prior Action Item Review

4. Continuing Business

Rechartering

Iain's adding our new Open Notice editors. Will ask staff to do an eVote.

Mark made a question about the name. What's the status there? Sent a quick note

Quorum

Joe ask Lionel to inquire about a new time with Iain for these meetings. If we can get a time that works for the "late" calls, Joe would like to shift to just two meeting times: the Open Notice time and the late call.

 

Redesign

 

Joe's tasked with getting email thread going about the redesign. Due to distractions, including IIW, that will start in earnest the last week of October.

We had discussed the notion of variable field descriptors and whether or not the two column model is worth keeping. Joe likes the two columns, but RealMe and the current label have a different approach to the field names.

 

Question: what do we call

  1. A row
  2. The left hand column
  3. The right hand column

If fields, then each row is a field. The left column is the field name/descriptor and the right column is the field value.

We could use spreadsheet nomenclature: cells, rows, columns. There's a big difference between talking about the "jurisdiction row" focuses on something less meaningful than "jurisdiction field". Also, if we transmit in non-tabular form, then we will probably still have field names and field values, e.g., in JSON or XML.

Attribute? Entry?

Field Name, Field Value

Field Description

Field Interrogative

The left hand column can/should be able to be displayed in any one of three formats, like a date in Excel: Field Name, Field Description, and Field Interrogative.
We like "field" as the referent for a given row, including either the value or the name depending on context. 
Interrogative: What question is the user asking as part of the decision making process to share or not to share?  Also could be thought as a teacher asking the question to the student as a pedagogical inquiry, or the anthopomorphized label asking in order to get the user to realize what's going on. 
Ok. So we have fields.
We'll define the Name, Values, Description, Interrogatives for each. Also choose which fields we want to keep, which are optional, and which are "expandable". Or also potential combinatoric rules about which must be shown in various combinations.

5. New Business

Report from the front

Lionel got some good feedback from two real-world banks that are data recipients for the RealMe PDS service. One liked it, the other chose to simply say "Please read our terms of services" instead of providing new, clearer data that might vary from the work already done by the legal team. 

 6. Action Items

None.

 

7. Next Meeting

  • Tuesday  October 22 : 9:00 am PDT, 12:00pm EDT,  5:00pm UK,
  • Wednesday October 23 : 2:00am JT, 5:00am NZT