Zegnat
https://github.com/Zegnat
•
Feb 16
Documenting from yesterday’s chat, because nobody could remember this and I can’t find it elsewhere:
- @tantek would like to keep parser changes conservative but is “amenable to expanding to any p- or e- = no implied p-name”.
- I have not been able to document any cases where more than this is necessary either.
So I think the (as of now) latest proposed spec change would be:
p-nameMUST NOT be implied if there are any explicitp-*ore-*properties, or any nested microformats.
Currently all mf2 items have a name property, because of implied name. If we change this, some code using the parsers could fail if it assumes a name is present.
Here too I will just document an answer given in chat, this time by @aaronpk:
may just mean it has to be released as a major version number [of the parsers]
Assuming something like semver is being used, any major version bump should signify possible API changes to the user. I too don’t think that would be an issue.
There might be an issue if someone is using parsers-as-a-service, e.g. always getting their mf2 parser output from php.microformats.io. But I don’t think anyone ever advertised their online parsers as a service?
