2012-07-03 Meeting on Context Description

Owned by Gottfried Zimmermann
Last updated: Jul 24, 2012Version comment
3 min read

Tue Jul 3, 12:00-14:00 UTC

Translate to my time zone

MINUTES

Notice

This meeting is being held as part of the Raising the Floor Consortium. The Raising the Floor membership agreement, in particular its IPR policy, applies to the contents of the meeting.

Attendance

  • Christophe, Gottfried
  • Claudia
  • Jim
  • Liddy
  • Vassilis
  • Andres
  • Andy
  • Gregg

Approval of last minutes

Minutes 2012-06-26 Meeting on Context Description approved.

Review of the Context Description table

See Context Description.

Do we want to give names to context or describe their functional requirements?

  • Continuum between giving names and give exact data.
  • E.g. "Home" is not a globally unique environment, it expresses a person's own home environment. "Home" is a name for a situation rather than describing the situation in detail.
  • Looking at terms describing the environment of the user using a product.
  • Useful for disambiguating a situation.
  • Two types of context properties: giving names (idiosyncratic) vs. data description

How to go about schema.org?

  • Schema.org can provide properties for location & activities
  • AccessForAll Metadata is doing accessibility metadata in schema.org (learning resources people)
  • Schema.org is search-engine driven
  • We could define a new object "Context", and link existing terms as fields (e.g. coffee shop)
  • Light-weight alternative: Just use the labels of the classes, e.g. "CafeOrCoffeeShop".

What to do about conditions that contain context properties that have undefined values?

  • Environmental data is typically patchy
  • Some property values may be undefined
  • "Try harder" concept: Use a simple match first, and if it doesn't work, use a more sophisticated matching.
  • Fuzzy logic: compute with undefined values, and if the condition evaluates to undefined, don't use the preference
  • Alternative: Assume default values. Easier to compute.
  • Device/environment could ask the user for values.
  • Can this be implementation specific? - But it can make a big difference.
    • Should be known by an entity writing a preference into a user profile.
  • We should also connect to the device properties group.

Next steps

  • Have a discussion with Dan Brickley on schema.org
  • People fill in terms in Context Description table

Action Items

Fill table at http://wiki.gpii.net/index.php/Context_Properties with information from other projects and standards:

  • Vassilis: User Profile Ontology, paper on context modeling, SOUPA ontologies
  • Claudia: ISO 9241-11 Annex A
  • Christophe: RFCs 4589 & 4480
  • Andy: Schema.org & ISO/IEC 24751
  • Gottfried: Contact somebody from MyUI
  • Andres: UsiXML & ISO/IEC 24756
  • Gottfried: WHO ICF, ISO/IEC 24752

See also: ISO 8601, XML Schema Definition - Part 2

Future Meetings

Possible dates & times (to be announced by Gottfried ahead of the meeting):

  • Wed Jul 11, 12-14 UTC = 14-16 CET (not available: Gregg, Christophe, Claudia)
  • Tue Jul 17, 12-14 UTC = 14-16 CET (not available: Gottfried)
  • Tue Jul 24, 12-14 UTC = 14-16 CET
  • Tue Jul 31, 12-14 UTC = 14-16 CET

Future Agenda Items

Bridge

1. To talk free using Web click. https://www3.gotomeeting.com/join/705233502
Be sure to set AUDIO to Mic and Speaker (VoIP) - a headset is recommended.

2. Or, call in using your telephone.

Meeting ID: 705-233-502

Australia: +61 (0) 7 3123 6029
Austria: +43 (0) 7 2088 1400
Belgium: +32 (0) 92 98 0592
Canada: +1 (416) 900-1165
Denmark: +45 (0) 69 91 88 62
Finland: +358 (0) 942 41 5778
France: +33 (0) 182 880 456
Germany: +49 (0) 898 7806 6461
Ireland: +353 (0) 14 845 976
Italy: +39 0 247 92 12 39
Netherlands: +31 (0) 208 080 379
New Zealand: +64 (0) 4 974 7215
Norway: +47 21 03 58 96
Spain: +34 911 82 9782
Sweden: +46 (0) 313 613 558
Switzerland: +41 (0) 225 3314 51
United Kingdom: +44 (0) 203 535 0621
United States: +1 (786) 358-5410
Access Code: 705-233-502