Errata is very loosely described, so I was just taking a best guess to get this thing moving.
Where should an errata section go? In the meta (e.g. an added section 9) or in the main document? (in RFCs, I think amendments are usually referenced in the main document using some kind of annotation/identifier referencing an errata section at the end of the document?) Thanks On Friday, January 11, 2019 at 5:25:25 PM UTC+1, Larry Garfield wrote: > > On Friday, January 11, 2019 3:37:07 AM CST Rasmus Schultz wrote: > > I accidentally opened the PR against the wrong project! > > > > Sorry about that. > > > > Here's the correct PR: > > > > https://github.com/php-fig/fig-standards/pull/1134 > > Changing the body of the spec itself is a no-go. "Addresses a problem > with > the existing specification" is what Errata are for, and what should be > used > here. > > I'm still mostly agnostic on the clarification itself (I haven't really > dug > into the problem space enough to say what the preferred behavior should > be), > but the only way forward is to add an Errata section to the metadoc that > includes appropriate "SHOULD" statements and not touch the spec file > itself. > > This PR as filed is unmergable. > > --Larry Garfield -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/4170f656-1c2c-45a4-ba6f-bf11c73dde05%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
