RDF-DEV Community Group - Activity in 2018
No matches.
Participants
-
3 organizations joined.
-
K Health joined.
-
J. Paul Getty Trust joined.
-
Ordina joined.
-
GitHub
w3c/EasierRDF
-
47 issues opened.
-
Transparently merge rdf: and rdfs: namespaces w3c/EasierRDF#52, by @dbooth-boston.
-
Relationship to the Web of Things w3c/EasierRDF#51, by @draggett.
-
Profile: Exactly one type per representation of a resource w3c/EasierRDF#50, by @azaroth42.
-
Popular use cases for graph data w3c/EasierRDF#49, by @draggett.
-
Different kinds of identifiers w3c/EasierRDF#48, by @draggett.
-
Scope & intention? w3c/EasierRDF#46, by @ktk.
-
Property Graphs w3c/EasierRDF#45, by @draggett.
-
Nobody knows who does what with what w3c/EasierRDF#43, by @HughGlaser.
-
Maybe "datatype" should be in the RDF Graph explicitly w3c/EasierRDF#42, by @HughGlaser.
-
Idea: Material to be put in an undergraduate DB or WebDev unit w3c/EasierRDF#41, by @HughGlaser.
-
Spoggy easy create & read graphs w3c/EasierRDF#40, by @scenaristeur.
-
SPARQL Triplestore and Reasoning Performance w3c/EasierRDF#39, by @dbooth-boston.
-
Lack of Full OWL2 Support in Triplestores w3c/EasierRDF#38, by @dbooth-boston.
-
Lack of RDF Visualisation Software w3c/EasierRDF#37, by @dbooth-boston.
-
test issue with no label w3c/EasierRDF#36, by @dbooth-boston.
-
Lack of a Good Editor w3c/EasierRDF#35, by @dbooth-boston.
-
Idea: Higher-level RDF language w3c/EasierRDF#34, by @dbooth-boston.
-
Idea: Build powerful query engines w3c/EasierRDF#33, by @dbooth-boston.
-
Idea: Build JavaScript libraries that work in the browser w3c/EasierRDF#32, by @dbooth-boston.
-
Idea: Base Linked Data on a JavaScript API w3c/EasierRDF#31, by @dbooth-boston.
-
Idea: Attract JavaScript front-end developers w3c/EasierRDF#30, by @dbooth-boston.
-
No standard way to map a JSON predicate to a URI w3c/EasierRDF#29, by @dbooth-boston.
-
Lack of a standard rules language w3c/EasierRDF#27, by @dbooth-boston.
-
Lack of standard RDF canonicalization w3c/EasierRDF#26, by @dbooth-boston.
-
Vocabulary for new semantic extensions w3c/EasierRDF#25, by @dbooth-boston.
-
Decouple semantics from data model w3c/EasierRDF#24, by @dbooth-boston.
-
Language-tagged strings w3c/EasierRDF#22, by @dbooth-boston.
-
Literals as subjects w3c/EasierRDF#21, by @dbooth-boston.
-
Standardized n-ary relations (and property graphs) w3c/EasierRDF#20, by @dbooth-boston.
-
Blank nodes w3c/EasierRDF#19, by @dbooth-boston.
-
IRI reuse and synonyms w3c/EasierRDF#17, by @dbooth-boston.
-
Easier-to-use competitors w3c/EasierRDF#16, by @dbooth-boston.
-
Define an easier profile of RDF w3c/EasierRDF#15, by @dbooth-boston.
-
Namespaces are lost in the RDF model w3c/EasierRDF#14, by @dbooth-boston.
-
Namespace proliferation w3c/EasierRDF#13, by @dbooth-boston.
-
IRI allocation w3c/EasierRDF#12, by @dbooth-boston.
-
Rejection of SQL and OO as Metaphors w3c/EasierRDF#11, by @dbooth-boston.
-
Lack of a Canonical Example w3c/EasierRDF#10, by @dbooth-boston.
-
Lack of Technology Framing w3c/EasierRDF#9, by @dbooth-boston.
-
Beginner friendly support w3c/EasierRDF#8, by @dbooth-boston.
-
Beginner friendly tutorials / documentation w3c/EasierRDF#7, by @dbooth-boston.
-
No clear entry point w3c/EasierRDF#6, by @dbooth-boston.
-
Moribundity of Tools w3c/EasierRDF#5, by @dbooth-boston.
-
Overview of an RDF triple store w3c/EasierRDF#4, by @dbooth-boston.
-
Lack of automated feedback / validation w3c/EasierRDF#3, by @dbooth-boston.
-
Tools are scattered w3c/EasierRDF#2, by @dbooth-boston.
-
Category: Big ideas w3c/EasierRDF#1, by @dbooth-boston.
-
-
3 issues closed.
-
Scope & intention? w3c/EasierRDF#46.
-
test issue with no label w3c/EasierRDF#36.
-
Category: Big ideas w3c/EasierRDF#1.
-
-
25 issues received 135 new comments.
-
Blank nodes w3c/EasierRDF#19 (24 comments by @afs, @dbooth-boston, @draggett, @HughGlaser, @kidehen, @rnavarropiris, @william-vw)
-
Lack of a Good Editor w3c/EasierRDF#35 (19 comments by @cyocum, @draggett, @jeff-zucker, @jmrog, @ktk, @namedgraph, @william-vw)
-
IRI reuse and synonyms w3c/EasierRDF#17 (17 comments by @chiarcos, @dbooth-boston, @draggett, @HughGlaser, @william-vw)
-
Define an easier profile of RDF w3c/EasierRDF#15 (11 comments by @azaroth42, @dbooth-boston, @HughGlaser, @namedgraph)
-
No clear entry point w3c/EasierRDF#6 (10 comments by @awwright, @dbooth-boston, @iherman, @mkbergman, @ontoconsult)
-
Transparently merge rdf: and rdfs: namespaces w3c/EasierRDF#52 (10 comments by @awwright, @cyocum, @dbooth-boston, @HughGlaser, @namedgraph)
-
Scope & intention? w3c/EasierRDF#46 (9 comments by @afs, @bergos, @dbooth-boston, @kidehen, @laurentlefort)
-
Language-tagged strings w3c/EasierRDF#22 (7 comments by @dbooth-boston, @draggett, @HughGlaser, @iherman, @kasei)
-
Idea: Attract JavaScript front-end developers w3c/EasierRDF#30 (3 comments by @dbooth-boston, @joshuef, @RubenVerborgh)
-
Profile: Exactly one type per representation of a resource w3c/EasierRDF#50 (1 comment by @dbooth-boston)
-
Participants
-
1 participant joined.
-
Sandro Hawke (W3C) joined.
-
-
2 organizations joined.
-
Deque Systems, Inc. joined.
-
KONA joined.
-
Participants
-
13 participants joined.
-
Thomas Lörtsch joined.
-
Timothy Cook joined.
-
Carlos Tejo joined.
-
Austin Wright joined.
-
Jindřich Kolman joined.
-
Roman Evstifeev joined.
-
Andrea Wei-Ching Huang joined.
-
Thomas Bergwinkl joined.
-
Melvin Carvalho joined.
-
David Booth joined.
-
Pavlik elf joined.
-
Stefan Götz joined.
-
Masahide Kanzaki joined.
-
-
17 organizations joined.
-
IPTC - International Press Telecommunications Council joined.
-
Université de Lyon joined.
-
PJJK Limited joined.
-
Apache Software Foundation joined.
-
Google LLC joined.
-
Two Six Labs joined.
-
Linked Data, UAB joined.
-
Technische Universität Wien joined.
-
Uber joined.
-
CSIRO joined.
-
TPXimpact Scotland Limited joined.
-
Spec-Ops joined.
-
Skemu joined.
-
popokotea joined.
-
Seme4 Limited joined.
-
Universidad Politécnica de Madrid joined.
-
Institut National de la Statistique et des Études Économiques joined.
-