Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues re. Primer - here /HTML #488

Open
sebilasse opened this issue Jan 14, 2025 · 2 comments
Open

Issues re. Primer - here /HTML #488

sebilasse opened this issue Jan 14, 2025 · 2 comments
Labels
pending-closure-in-7-days This issue will be closed in 7 days after review Waiting for Commenter

Comments

@sebilasse
Copy link

sebilasse commented Jan 14, 2025

I hope, this is the right place to file issues re. https://www.w3.org/wiki/ActivityPub/Primer/HTML

Proposing that, if any section is a work in progress to write t.b.c. in the end.

Otherwise, we say to include blockquote in the "minimum set" (Note and Article)
I see the problem that a lot of author and source markups get lost, if we do not mention
<footer> and <cite> as well.
For example, see the recommendations in a "popular CSS framework" or at MDN or at the W3C


re.

These are some of the common known good URL schemes:

Question - how about geo: ?
(et al.: please attend the very nice "Geosocial Taskforce")

@evanp
Copy link
Collaborator

evanp commented Jan 17, 2025

  • So, the primer covers best practices and guidance for publishers and consumers. Publishers should probably only publish elements, attributes and protocols that are widely accepted by consumers; consumers should be aware of the elements, attributes and protcols that publishers widely use.

It's not normative, although it makes sense for us to consider normative guidelines for Activity Streams 2.0 summary and content HTML properties in a future version. This has been difficult for implementers in the past. There are FEPs, like FEP b2b8, that give more guidance on HTML usage.

I think right now the main guidance on HTML usage is the Mastodon supported elements and attributes. It'd be good to get this moved in.

So, I think it makes sense to make suggestions on that wiki page, with the expectation that Postel rules apply.

@evanp evanp added Waiting for Commenter pending-closure-in-7-days This issue will be closed in 7 days after review labels Jan 17, 2025
@evanp
Copy link
Collaborator

evanp commented Jan 17, 2025

The decision on how to handle a best practice subset of HTML to support is discussed in #419 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-closure-in-7-days This issue will be closed in 7 days after review Waiting for Commenter
Projects
None yet
Development

No branches or pull requests

2 participants