-
Notifications
You must be signed in to change notification settings - Fork 4
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
Clarify that this is just for mf2 users or generalize #2
Comments
Generalizing is definitely the intent, the mf2 terms were used as one example to conform to. |
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). |
The title and description of the specification makes this sound really general and useful even outside the world of mf2.
http://socialwg.indiewebcamp.com/irc/social/2015-12-02#t1449103272809
The text was updated successfully, but these errors were encountered: