Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Clarify that this is just for mf2 users or generalize #2
The title and description of the specification makes this sound really general and useful even outside the world of mf2.
changed the title from
Generalize to support serializations other than mf2
Clarify that this is to enable mf2 integration, or generalize
Dec 3, 2015
The existing algorithm uses property names outside of any particular syntax. While these names are based on mf2 (most commonly used vocab for the properties mentioned), the algorithms (or at least portions thereof) are applicable to other formats as well, e.g. the steps that use "name" and "content" to determine if a post is a note vs. an article are quite useful for making this determination for untyped RSS and Atom feeds.
I think that sort of "equivalence in other syntaxes" can be documented externally in a wiki rather than the draft itself so I'd like to close this issue without needing to change the spec for it, and document that sort of thing on the IndieWeb wiki instead, since there's potentially numerous other syntaxes that could be documented like that in the future.
Since Atom and RSS are both well established / unchanging at this point, it's worth at least specifying the obvious equivalents of name/content in both of those for those wanting to do at least article/note detection from those feeds (which is a real use-case from various social networks).