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
u-comment - optionally embedded (or nested?) h-cite(s), each of which is a comment on/reply to the parent h-entry.
The h-entry spec identified p-comment as a optionally embedded (or nested?) h-cite(s), each of which is a comment on/reply to the parent h-entry. Being as the URL would be proper for a citation in most cases, it should be a u proposal.
u-comment - identifies the element as a comment on the h-entry, for comment discovery when reading an h-entry. Optionally an embedded h-cite
Per change-control, I think we still need 3+ consuming implementations.
Stable features (e.g. Core Properties) must in addition be published and consumed in the wild on multiple sites by multiple implementations (3+ different sites and implementations for publishing and consuming)
u-comment - optionally embedded (or nested?) h-cite(s), each of which is a comment on/reply to the parent h-entry.
The h-entry spec identified p-comment as a
optionally embedded (or nested?) h-cite(s), each of which is a comment on/reply to the parent h-entry.
Being as the URL would be proper for a citation in most cases, it should be a u proposal.u-comment -
identifies the element as a comment on the h-entry, for comment discovery when reading an h-entry. Optionally an embedded h-cite
There seem to be a sufficient amount of examples. https://indieweb.org/comments#IndieWeb_Examples
The text was updated successfully, but these errors were encountered: