fix: id and state in Data Model
#17
Conversation
+ `id` is a IRI or bnode (not string). + `notify:state` (not `id`) can be used to set `Last-Event-ID`. + Add prefixes to properties in Data Model.
src/sections/data-model.md
Outdated
| <dt id="notification-property-id"><code>*id* <xs:string></code> | ||
| <dd> an opaque identifier for the notification. Can be used to set `Last-Event-ID` in a subsequent [PREP] notifications request. | ||
| <dt id="notification-property-id"><code>*id* <rdfs:subject></code> | ||
| <dd> an unique identifier for a notification. |
There was a problem hiding this comment.
| <dd> an unique identifier for a notification. | |
| <dd> a unique identifier for a notification. |
But why not just say URI or IRI here? I don't have the full view of the spec right now, if that's clear from the rest of the text, okay.
There was a problem hiding this comment.
Because I cannot find an authoritative source for that. I researched RDF specifications quite a bit.
There was a problem hiding this comment.
OK, perhaps it would suffice to staying close JSON-LD language here. See @id in https://www.w3.org/TR/json-ld11/#syntax-tokens-and-keywords
There was a problem hiding this comment.
I have seen that. I am convinced a notification should not be a bnode e.g. para 3 here.
But, I cannot find any such description of subjects, closest being one you point to above, which allows bnodes. Even that does not have any analogue in RDF specs. The language used in specifications is obtuse and all over the place.
| @@ -8,13 +8,13 @@ A [PREP] notification from an LDP Resource on a [=Solid server=] MUST have the f | |||
|
|
|||
| <dl> | |||
|
|
|||
| <dt id="notification-property-id"><code>*id* <xs:string></code> | |||
| <dd> an opaque identifier for the notification. Can be used to set `Last-Event-ID` in a subsequent [PREP] notifications request. | |||
| <dt id="notification-property-id"><code>*id* <rdfs:subject></code> | |||
There was a problem hiding this comment.
Is mention of rdfs:subject necessary?
There was a problem hiding this comment.
This is the closest thing I could find that indicates, that id is expected to be IRI. How else can I specify the type of id using RDF?
There was a problem hiding this comment.
See also https://www.w3.org/TR/xmlschema11-2/#anyURI
I don't have a strong opinion on only using IRI here. So, I'll dial back and suggest that a Note about what implementers may want to consider can be useful.
There was a problem hiding this comment.
Happy for you to suggest one. But in another PR so that it can be traced!
There was a problem hiding this comment.
Saying IRI should be enough; using rdf:subject seems confusing and possibly incorrect.
There was a problem hiding this comment.
@elf-pavlik The context above as @csarven points out is that, JSON-LD spec allows @id to be IRI or bnode. The latter, though not meaningful, is not expressly prohibited, and I don't want to add additional constraints without reason. I open to suggestion as to how to specify type for id.
There was a problem hiding this comment.
in #18 :Notification IRI { requires it to be an IRI
There was a problem hiding this comment.
I think it is an improvement once rdfs:subject is replaced with IRI
I created #18 to possibly improve it even further
| @@ -8,13 +8,13 @@ A [PREP] notification from an LDP Resource on a [=Solid server=] MUST have the f | |||
|
|
|||
| <dl> | |||
|
|
|||
| <dt id="notification-property-id"><code>*id* <xs:string></code> | |||
| <dd> an opaque identifier for the notification. Can be used to set `Last-Event-ID` in a subsequent [PREP] notifications request. | |||
| <dt id="notification-property-id"><code>*id* <rdfs:subject></code> | |||
There was a problem hiding this comment.
| <dt id="notification-property-id"><code>*id* <rdfs:subject></code> | |
| <dt id="notification-property-id"><code>*id* IRI</code> |
There was a problem hiding this comment.
IRI itself is not a data type...
There was a problem hiding this comment.
only literals have data type, not named or blanked nodes https://www.w3.org/TR/rdf11-concepts/#section-Graph-Literal
idis a IRI or bnode (not string).notify:state(notid) can be used to setLast-Event-ID.Fixes #11.