-
Notifications
You must be signed in to change notification settings - Fork 11
Meetings
Table of Contents
date & time: 2015-10-09T17:00Z
chatroom and scribe: https://gitter.im/rdfjs/public
VoIP: G+ Hangouts (link available in chatroom 10 min before call starts)
Currently we don't have official communication channels except mailing list, we also have two wikis, we could use first 5 min of the meeting to agree at least on some of the common online collaboration spaces.
https://w3c.github.io/modern-tooling
- Chat
- IRC: irc://irc.w3.org:6665/#rdfjs
- Gitter: https://gitter.im/rdfjs/public (currently no queue management)
- List
- mailto:public-rdfjs@w3.org
- Wiki
- Mediawiki: http://www.w3.org/community/rdfjs/wiki/Main_Page (mediawiki syntax)
- Github wiki of: https://github.com/rdfjs/rdfjs.org (markdown syntax + git access - enables use of http://git2prov.org/)
- alternative: /wiki directory in: https://github.com/rdfjs/rdfjs.org
- Website
-
http://rdfjs.org (registered by @l00mi)
- will in visible way reference https://www.w3.org/community/rdfjs/
- Issues & Actions
- website: https://github.com/rdfjs/rdfjs.org
- workstreams? (Task Forces could make that choice independently)
- Teleconferences
- MIT/WebEx (official W3C, proprietary platform)
- G+ Hangout (proprietary)
- https://talky.io/ (failed kickstarter to open source)
- https://meet.jit.si/ (open source)
- social media
- https://twitter.com/rdfjs (@elf-pavlik can share credentials)
- misc
- please consider making visibility of your membership in github orga public! (ATM only 7/24 ) https://github.com/orgs/rdfjs/people
- http://alioth.debian.org (new mailing list and git repository) proposed by Jonas Smedegaard
- Representing triples and quads (see Task Force)
- Use cases (see Task Force)
- Mapping Projects (dependencies, maintainers/contributors, specs, features)
proposed by: @bergi & @RubenVerborgh
- taskforce: what & who
- use cases and code snippets
- targets
- definitions of common terms
- low-level API used by parsers, by, serializers, and by high-level libraries
- guideline for applications/parser developers to decide when to use low-level API or high level libraries
- specification
- specification test suite
- discussion topics
- callbacks / promises / …
Action: find editor
The mission of the rdfjs Community Group is to coordinate development of a coherent RDF stack for javascript browser and stand-alone applications. This platform will address at least:
- parsing standard formats like JSON-LD, Turtle, Trig, RDFa and RDF/XML.
- querying RDF data with SPARQL 1.1. and may include
- classification and semantic validation with OWL 1.1
- syntactic data validation with ShEx or SHACL.
This group will examine use cases to make informed choices between:
- accessor methods vs. fixed properties for triples and graphs.
- streaming vs. promises for long-running functions.
Deliverables: @@ not needed because it repeats the mission statement?
Proposal: monthly telecon
This group currently has no chairs. Please check boxes for individuals you wish to select as chairs, then push the Propose button at the bottom of the page.
https://www.w3.org/community/about/tool/#choose-chair
- List
-
"Telecon March 26th 18:00UTC (tomorrow!)" https://lists.w3.org/Archives/Public/public-rdfjs/2015Mar/0010.html
- "Contemporary Messages Sorted by Thread" https://lists.w3.org/Archives/Public/public-rdfjs/2015Mar/thread.html#msg10
-
"Telecon March 26th 18:00UTC (tomorrow!)" https://lists.w3.org/Archives/Public/public-rdfjs/2015Apr/0000.html
-
-
etherpad lite
live doc*:
-
outline, objectives, tasks, field links:
-
apiVersion: apps.gitlab.com/v1beta2 kind: Runner metadata: name: dev spec: gitlabUrl: https://gitlab.example.com token: gitlab-runner-secret ca: custom-tls-ca