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
While such microsyntaxes MAY be used within the values of the content, name, and summary properties on an Activity Streams Object, implementations SHOULD NOT be required to parse the values of those properties in order to determine the appropriate routing of notifications, categorization or linking between objects. Instead, publishers SHOULD make appropriate use of the vocabulary terms provided specifically for these purposes.
proposed outcome
either:
lift this bit of text out of the non-normative section and put it into a normative section (perhaps by making the section normative then making a new subsection 5.6.1 be non-normative examples)
remove use of normative text
errata? next version?
The text was updated successfully, but these errors were encountered:
So, this probably deserves more research on how the W3C manages normative language like MAY, MUST, SHOULD in non-normative sections. I will research that editorial policy and we can make an erratum to bring this section in line with W3C best practices.
I think it makes a lot of sense to call out that there are addressing properties already defined by AS2 Vocabulary which are preferable for delivery and routing. However, at least one tag object type, Hashtag, is widely used for delivery and routing, and it's possible to do routing by other properties (content, summary, name). So, non-normative guidance here is probably preferable to normative SHOULD NOT language.
W3C best practice is to avoid using RFC2119 language, even if it's used in lowercase, in non-normative text. Various other phrasings can be used, depending on the specifics of the text in question.
Second-best practice is to make sure that non-normative use of RFC2119 terms always puts it in lowercase ... but humans very often interpret the lowercase as if it were uppercase; hence the best practice, above.
From https://www.w3.org/TR/activitystreams-vocabulary/#microsyntaxes
proposed outcome
either:
errata? next version?
The text was updated successfully, but these errors were encountered: