- From: Erik Wilde <notifications@github.com>
- Date: Fri, 15 Apr 2016 04:36:05 -0700
- To: w3c/manifest <manifest@noreply.github.com>
Received on Friday, 15 April 2016 11:36:51 UTC
> Doesn't that defeat the purpose of extension points? Extension points > are included in algorithms to avoid monkey patching. The extension point > is defined so that custom processing can be defined and executed at that > point in a way that doesn't require changes to the base algorithm (the > definition of a monkey patch). i think that's a good starting point. one of the important things of a spec is always the processing model, though. so what you should never do (and the underlying spec should outrule this in the strongest terms) is to change the processing of the core vocabulary. in other words, somebody not knowing your extension, but only knowing the core set, should be able to process the manifest and get meaningful and correct behavior out of it. if that's not the case, something is wrong. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/452#issuecomment-210426928
Received on Friday, 15 April 2016 11:36:51 UTC