Community Call/05

Invitation

The invitation, including the Zoom link, is here.

Agenda

• Goal today: best practices for working together, not actually solving the problems
• Communication channels and rationale
  • Communication on the wiki:
    • use {{reply_to|Podehaye}} to ping someone (alert when they log in, email if configured to receive emails)
    • use ~~~~ to sign, see https://en.wikipedia.org/wiki/Wikipedia:Signatures
• Who reads from the wiki?
  • once in a while:
    • Le Temps for their investigation
  • continuously:
    • popup, introduced by MediaWiki:Common.js [video timecode 15:00]
    • opt-in/opt-out gadgets, introduced via MediaWiki:Gadgets-definition [video timecode 28:28]
    • eventually augmented by user script (e.g. User:Podehaye/common.js) [video timecode 25:25]
• hence: need for an ontology
  • How do we structure Internet of Things (IoT) devices like Tesla Cars or Amazon Echo / Alexa?
  • Should we make on item by model? Group of model?
  • One item by services? But what is the services? Typically Amazon Echo devices are linked to Alexa services, but they may differ in data collection.
  • Can we do a type of data collection and inject it in all Tesla Cars Model?
  • How do we index data controllers? Etc?
  • Project:Ontology
• Overview of the wiki base technology. [video timecode 39:41]
  • I haven't really has it explained to me. I understand it loosely as wiki plus NoSQL triplestore Db but high level tech explanation would be good. Help:Wikibase technology
  • Namespaces (see advanced search)
• Help:Templates
  • Including importantly how to enable a new one
  • Template syntax (maybe that might need to be a separate call)
• Help:SPARQL
  • Querying .. whatever the equivalent of SQL is
  • How to generate visual query results (nodes, tables etc)
• Merging?
• Update queries/batch operations Help:Quick Statements
• Other cool/useful stuff you can do that I might not be aware of (edited).>

USEFUL TOOL: Descriptions: Show the description of items and properties when hovering them. https://www.wikidata.org/wiki/MediaWiki:Gadget-Descriptions.js

• Fill the next agenda, for Community Call/06

Final video

• https://invidio.us/watch?v=D950_JoNDPI

Key timepoints:

• [15:00] Explanation of how the GDPR request generator template is loaded:
  • [15:00] MediaWiki:Common.js (Javascript)
    • [15:44] MediaWiki:Access.js (Javascript)
      • [16:28] Template:Menu (wikibase template language)
        • [16:54] Template:MailtoAccess (wikibase template language)
          • [17:42] Template:mailto (wikibase template language)
          • (not shown) Template:wikidata (wikibase template language)
          • [19:20] Template:Access (wikibase template language)
            • [20:53] Module:wd (Lua)
• [25:25] Explanation of User's own common.js
• [28:28] Explanation of Gadgets MediaWiki:Gadgets-definition
  • [28:32] QuickPresets Gadget - demo. Code is at MediaWiki:Gadget-QuickPresets.js
  • [28:58] How to turn Gadgets on and off
• [39:41] Explanation of Wikibase Technology: SQL datastore of RDF triples. There is a CRUD API that interfaces with that. But it also uses a graph database to enable SPARQL queries. The SQL database gets fed into BlazeGraph using the 'updater' but this has a delay (a second to several hours). So query results may not be as up to date as what is in the database.
  • [42:05] how to access SPARQL query service
  • Help:Wikibase_technology
  • [43:00] API [[API help page]]
    • [43:12] API Sandbox
    • The moment you make an HTTP Post request via the API, that goes into the wiki's SQL database.
    • [43:40] Explanation of what a "claim" is. - it is effectively an RDF triple. e.g. Item - Property - Item or Item - Property - String/datatype
    • Wikibase has a separate layer, its interpretation of the underlying RDF triples.
• [46:29] Namespaces