- From: Andreas Kuckartz <a.kuckartz@ping.de>
- Date: 21 Aug 2014 21:24:52 +0200
- To: "public-socialweb@w3.org" <public-socialweb@w3.org>
- Cc: "activity-streams@googlegroups.com" <activity-streams@googlegroups.com>
James M Snell:
> Activity Streams 2.0 already has an "id" property that is mapped to
> the JSON-LD "@id". While this property is required to be an absolute
> IRI, it is not always dereferenceable and for backwards compatibility,
> we cannot necessary declare that it must be. For most cases, however,
> using "id" will be sufficient.
...
> {
> "objectType": "person",
> "id": "urn:example:person:123456",
> "url": "http://example.org/~joe"
> }
...
> The point is that AS1 has always made a distinction between the static
> never-changing identifier (id) and the reference to a displayable page
> about the object (url). In cases where those are one and the same, id
> works just fine.
Thanks, now I see where the core of the problem is: There is a property
which is unique but might not be dereferenceable and another optional
property which is unique (is it?) and dereferenceable.
I am not happy with that and hope that we can simplify this without
endangering backwards compatibility.
What can be done if we differentiate between requirements for clients
and servers ?
Can id and url be combined then for new servers to something like either
"@id": "http://example.org/person/123456"
or
"@id": "http://example.org/~joe"
?
Cheers,
Andreas
Received on Thursday, 21 August 2014 19:25:23 UTC