You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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")
The text was updated successfully, but these errors were encountered:
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 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
andArticle
)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.
Question - how about
geo:
?(et al.: please attend the very nice "Geosocial Taskforce")
The text was updated successfully, but these errors were encountered: