- From: elf Pavlik via GitHub <sysbot+gh@w3.org>
- Date: Sun, 15 Apr 2018 19:01:06 +0000
- To: public-hydra-logs@w3.org
In UC5 client send this payload (a single blank node)
```jsonld
{
"@context": "https://example.org/api/context.jsonld",
"@type": "schema:Event",
"eventName": "My brand new event",
"eventDescription": "Hope it will work",
"startDate": "2017-04-19",
"endDate": "2017-04-19"
}
```
It could as well use single (default) graph
```jsonld
{
"@context": "https://example.org/api/context.jsonld",
"@graph": [
{
"@type": "schema:Event",
"eventName": "My brand new event",
"eventDescription": "Hope it will work",
"startDate": "2017-04-19",
"endDate": "2017-04-19"
}
]
}
```
or something like this (which seems to cheat by not providing `@base` in the request)
```jsonld
{
"@context": "https://example.org/api/context.jsonld",
"@graph": [
{
"@id": "",
"@type": "foaf:Document",
"foaf:primaryTopic": "#this"
}
{
"@id": "#this",
"@type": "schema:Event",
"eventName": "My brand new event",
"eventDescription": "Hope it will work",
"startDate": "2017-04-19",
"endDate": "2017-04-19"
}
]
}
```
@RubenVerborgh maybe you have better idea how Solid uses such relative IRIs in POST payload without providing explicit `@base` ? It seems to me that Solid client expect server to use IRI it will assign to the resource as the value for `@base`.
@tpluscode while I think we should eventually ensure that Hydra supports scenarios like in last two snippets. I think we should start with clarifying in UC5 how after posting a blank node, following responses to that resource (or collection embedding it) have representation with a named node (`@id` with IRI denoting the resource)
--
GitHub Notification of comment by elf-pavlik
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/162#issuecomment-381429691 using your GitHub account
Received on Sunday, 15 April 2018 19:01:10 UTC