Re: First draft of ActivityPub HTML Discovery report

>
> It seems the id is tying the person’s identifier to the file name
> (person-1.jsonld)
>

 I think it's just illustrative of what is on the other end of the URL.
Valid but maybe not typical, but some servers are configured to serve
content-types based on file extensions so I'm sure there are real world
examples


On Sat, Nov 16, 2024 at 7:52 AM Melvin Carvalho <melvincarvalho@gmail.com>
wrote:

>
>
> so 16. 11. 2024 v 4:30 odesílatel Evan Prodromou <evan@prodromou.name>
> napsal:
>
>> Hello, all. There's a first draft of the ActivityPub HTML Discovery
>> report here:
>>
>> https://swicg.github.io/activitypub-html-discovery/
>>
>> It includes:
>>
>>    - a description of discovery as a topic
>>    - motivating use cases for HTML-to-ActivityPub discovery and
>>    ActivityPub-to-HTML discovery
>>    - techniques for discovering equivalent objects and authors
>>    - verification techniques for object discovery and author discovery
>>    - best practices for consumers and publishers
>>
>> It would be great to collect issues here:
>>
>> https://github.com/swicg/activitypub-html-discovery/issues
>>
>> At least one major feature still needs to be written up -- discovering
>> equivalent actors using rel="me". Tantek, can we work on this together?
>>
>
> This looks wrong to me:
>
> {
>   "@context": "https://www.w3.org/ns/activitystreams",
>   "id": "https://ap.example/some/path/person-1.jsonld",
>   "type": "Person",
>   "name": "Person One",
>   "url": "https://html.example/profile/person-1.html"
> }
>
> It seems the id is tying the person’s identifier to the file name
> (person-1.jsonld), which feels like a conflation of concepts. That said, I
> assume this is an intentional design choice—perhaps a feature, not a bug?,
> that AP will just have to live with.
>
> No need to log an issue; just sharing the thought.
>
> Evan
>>
>>
>>
>>