-
Currently the "Latest" links on https://json-ld.org/spec/ (and in the header menu) are incorrect--as they point to the last draft from the CG and not the current in-progress WG specs.
Consequently,…
-
(Spin-off from #42)
There may be a number of prefixes that we could 'predefine', i.e., having them part, formally, of an initial `@context`. This would simplify to encourage users to use terms from…
-
The current consensus is that a WP MUST have a Primary Entry Page, i.e. an HTML page.
I has been argued by the Audio TF that audio books don't have HTML pages and adding a dummy page to a package …
-
We have the use case of fetching all Property values at once, i.e., with a single request. This is very common in industrial systems, but also the Web recently picked up such ways to reduce round-trip…
-
(This is a meta-issue)
Many existing JSON structures use simple "short cut" properties when there is only a single piece of information known about an intermediate resource. For example, if only t…
-
Following up on the google group discussion here: https://groups.google.com/forum/#!topic/dataverse-community/rQWNllAyTu0
Dataverse should support and display Make Data Count (https://makedatacoun…
-
This is the first of four options that were the result of the meeting on Aug 3, 2018.
**Requirement**: A way to annotate JSON-LD Context with information about when and how it was generated, its i…
-
Consider the following inputs:
(1)
```json
{
"@graph": [{
"@id": "http://example.com/Flintstone",
"@type": [
"http://www.w3.org/ns/shacl#PropertyShape"
…
-
I want the following:
``` js
{
"@context": {
"type": "@type",
"profile": "@type"
},
"type": "cov:Coverage",
"profile": "cov:GridCoverage"
}
```
However this is not allowed. The playg…
-
Thank you to Siemens for presenting their [Simplified WoT Thing Description](https://w3c.github.io/wot-thing-description/proposals/simplified-td/) proposal to us today in the TD Serialization call.
…