JSON for Linked Data Community Group - Activity in 2011
No matches.
Participants
-
1 organization joined.
-
EAST Team, non-Member joined.
-
GitHub
json-ld/json-ld.org
-
5 issues opened.
-
Rename @literal to @value json-ld/json-ld.org#48, by @lanthaler.
-
Using the words subject, property and object might confuse some people json-ld/json-ld.org#47, by @lanthaler.
-
Define when an IRI is considered to be absolute and if IRI normalization is supported json-ld/json-ld.org#46, by @lanthaler.
-
Define if JSON-LD is case-sensitive or not json-ld/json-ld.org#45, by @lanthaler.
-
Support for @set coercion json-ld/json-ld.org#44, by @jmandel.
-
-
7 issues closed.
-
Define if JSON-LD is case-sensitive or not json-ld/json-ld.org#45.
-
IRI expansion within @context requires terms to be previously defined json-ld/json-ld.org#41.
-
Merge @type and @datatype json-ld/json-ld.org#31.
-
Merge @coerce with @context json-ld/json-ld.org#40.
-
Type Coercion is confusing json-ld/json-ld.org#34.
-
Are @subject and @iri redundant? json-ld/json-ld.org#15.
-
Remove MIME type parameter option "form=framed" from spec json-ld/json-ld.org#14.
-
-
1 issue reopened.
-
IRI expansion within @context requires terms to be previously defined json-ld/json-ld.org#41, by @lanthaler.
-
-
12 issues received 21 new comments.
-
IRI expansion within @context requires terms to be previously defined json-ld/json-ld.org#41 (5 comments by @gkellogg, @lanthaler)
-
Use of IRIs and CURIEs as @context keys json-ld/json-ld.org#43 (2 comments by @gkellogg, @lanthaler)
-
Make it clear where prefixes are allowed and when they are interpreted as prefixes json-ld/json-ld.org#38 (1 comment by @gkellogg)
-
json-ld/json-ld.org#16 (1 comment by @lanthaler)
-
Define when an IRI is considered to be absolute and if IRI normalization is supported json-ld/json-ld.org#46 (1 comment by @gkellogg)
-
json-ld/json-ld.org#14 (1 comment by @lanthaler)
-
json-ld/json-ld.org#8 (1 comment by @lanthaler)
-
Participants
-
2 participants joined.
-
Ted Guild (W3C) joined.
-
Kyle Simpson joined.
-
-
1 organization joined.
-
Open Geospatial Consortium joined.
-
GitHub
json-ld/json-ld.org
-
5 issues opened.
-
Use of IRIs and CURIEs as @context keys json-ld/json-ld.org#43, by @gkellogg.
-
Distinguishing a JSON-LD frame from a JSON-LD document json-ld/json-ld.org#42, by @msporny.
-
IRI expansion within @context requires terms to be previously defined json-ld/json-ld.org#41, by @gkellogg.
-
Merge @coerce with @context json-ld/json-ld.org#40, by @gkellogg.
-
@context should be at the top of the JSON-LD output in the playground json-ld/json-ld.org#39, by @lanthaler.
-
-
10 issues closed.
-
Make it clear when a term in JSON-LD is interpreted as IRI json-ld/json-ld.org#25.
-
Multiple contexts json-ld/json-ld.org#32.
-
Simplify "Multiple Typed Literals for a Single Property" json-ld/json-ld.org#33.
-
Basic: Enumerate the goals of the syntax more clearly json-ld/json-ld.org#3.
-
Define if data in context documents is ignored json-ld/json-ld.org#36.
-
Distinguishing a context document from an instance document json-ld/json-ld.org#30.
-
Add compact forms of language literals json-ld/json-ld.org#29.
-
Data round-tripping issues: create a JSON vocabulary json-ld/json-ld.org#35.
-
Clarify prefix expansion json-ld/json-ld.org#37.
-
@context should be at the top of the JSON-LD output in the playground json-ld/json-ld.org#39.
-
-
1 issue reopened.
-
Merge @type and @datatype json-ld/json-ld.org#31, by @lanthaler.
-
-
13 issues received 30 new comments.
-
Make it clear where prefixes are allowed and when they are interpreted as prefixes json-ld/json-ld.org#38 (4 comments by @gkellogg, @lanthaler)
-
Make it clear when a term in JSON-LD is interpreted as IRI json-ld/json-ld.org#25 (2 comments by @lanthaler, @msporny)
-
Define if data in context documents is ignored json-ld/json-ld.org#36 (2 comments by @lanthaler, @msporny)
-
Distinguishing a context document from an instance document json-ld/json-ld.org#30 (2 comments by @msporny)
-
IRI expansion within @context requires terms to be previously defined json-ld/json-ld.org#41 (1 comment by @gkellogg)
-
Distinguishing a JSON-LD frame from a JSON-LD document json-ld/json-ld.org#42 (1 comment by @lanthaler)
-
json-ld/json-ld.org#3 (1 comment by @msporny)
-
json-ld/json-ld.org#16 (1 comment by @lanthaler)
Participants
-
1 organization joined.
-
Mozilla Foundation joined.
-
GitHub
json-ld/json-ld.org
-
3 issues opened.
-
Make it clear where prefixes are allowed and when they are interpreted as prefixes json-ld/json-ld.org#38, by @lanthaler.
-
Clarify prefix expansion json-ld/json-ld.org#37, by @lanthaler.
-
Define if data in context documents is ignored json-ld/json-ld.org#36, by @lanthaler.
-
-
2 issues closed.
-
Should Normalization be moved to an external specification? json-ld/json-ld.org#27.
-
Split the spec into Syntax and API documents json-ld/json-ld.org#28.
-
-
10 issues received 16 new comments.
-
Make it clear where prefixes are allowed and when they are interpreted as prefixes json-ld/json-ld.org#38 (3 comments by @lanthaler)
-
Distinguishing a context document from an instance document json-ld/json-ld.org#30 (2 comments by @lanthaler)
-
Simplify "Multiple Typed Literals for a Single Property" json-ld/json-ld.org#33 (2 comments by @msporny)
-
Should Normalization be moved to an external specification? json-ld/json-ld.org#27 (1 comment by @lanthaler)
-
json-ld/json-ld.org#12 (1 comment by @lanthaler)
-
Participants
-
16 participants joined.
-
Pavlik elf joined.
-
Harry Halpin (W3C) joined.
-
David Peterson joined.
-
Ya Knygar joined.
-
Niklas Lindström (National Library of Sweden) joined.
-
Paul Scott joined.
-
Dominik Tomaszuk joined.
-
Jeff Sayre joined.
-
Antonio Garrote joined.
-
Shane McCarron joined.
-
Shane McCarron joined.
-
Ted Guild (W3C) joined.
-
Kevin Peno joined.
-
Markus Lanthaler (Google LLC) joined.
-
Ivan Herman (W3C) joined.
-
Gregg Kellogg joined.
-
-
3 participants left.
-
Kevin Peno left.
-
Shane McCarron left.
-
Ted Guild (W3C) left.
-
-
9 organizations joined.
-
Library of Congress joined.
-
LINKatu joined.
-
Google LLC joined.
-
University of Oklahoma joined.
-
OpenLink Software Inc. joined.
-
Vrije Universiteit joined.
-
INSIGHT - The Centre for Data Analytics joined.
-
Zope Corporation joined.
-
Digital Bazaar joined.
-
GitHub
json-ld/json-ld.org
-
13 issues opened.
-
Data round-tripping issues: create a JSON vocabulary json-ld/json-ld.org#35, by @lanthaler.
-
Type Coercion is confusing json-ld/json-ld.org#34, by @lanthaler.
-
Simplify "Multiple Typed Literals for a Single Property" json-ld/json-ld.org#33, by @lanthaler.
-
Multiple contexts json-ld/json-ld.org#32, by @lanthaler.
-
Merge @type and @datatype json-ld/json-ld.org#31, by @lanthaler.
-
Distinguishing a context document from an instance document json-ld/json-ld.org#30, by @lanthaler.
-
Add compact forms of language literals json-ld/json-ld.org#29, by @lanthaler.
-
Split the spec into Syntax and API documents json-ld/json-ld.org#28, by @msporny.
-
Should Normalization be moved to an external specification? json-ld/json-ld.org#27, by @msporny.
-
Drop @base and @vocab json-ld/json-ld.org#26, by @lanthaler.
-
Make it clear when a term in JSON-LD is interpreted as IRI json-ld/json-ld.org#25, by @lanthaler.
-
Remove explicit use of "semantic web" json-ld/json-ld.org#24, by @lanthaler.
-
Change the term Web Vocabulary to just vocabulary json-ld/json-ld.org#23, by @lanthaler.
-
-
9 issues closed.
-
Add support for NULL!? json-ld/json-ld.org#11.
-
Remove explicit use of "semantic web" json-ld/json-ld.org#24.
-
Change the term Web Vocabulary to just vocabulary json-ld/json-ld.org#23.
-
Specify forward slash escaping behavior for normalized output. json-ld/json-ld.org#22.
-
Should CURIEs be removed from the spec? json-ld/json-ld.org#20.
-
API return values (null values vs. Exceptions, framing) json-ld/json-ld.org#13.
-
Resolve inconsistencies in IANA section; add full syntax (e.g. EBNF) json-ld/json-ld.org#10.
-
Basic: Focus more on Linked Data less on RDF json-ld/json-ld.org#1.
-
Basic: What are relative URLs resolved against? json-ld/json-ld.org#2.
-
-
1 issue reopened.
-
Drop @base and @vocab json-ld/json-ld.org#26, by @lanthaler.
-
-
16 issues received 29 new comments.
-
Distinguishing a context document from an instance document json-ld/json-ld.org#30 (1 comment by @lanthaler)
-
json-ld/json-ld.org#13 (1 comment by @msporny)
-
json-ld/json-ld.org#10 (1 comment by @msporny)
-
json-ld/json-ld.org#1 (1 comment by @msporny)
-
json-ld/json-ld.org#2 (1 comment by @msporny)
-
Should Normalization be moved to an external specification? json-ld/json-ld.org#27 (1 comment by @gkellogg)
-
json-ld/json-ld.org#12 (1 comment by @lanthaler)