Update maturity level

[duckontheweb]

Should the Extension Maturity Classification be updated to Pilot since there are now a few implementations out there as well as a schema and examples?

[m-mohr]

I think the reason for not doing it was that there were some people discussing whether this extension should be split into multiple parts (see the open issues). An extension that seems to be a work in progress, shouldn't be Pilot.

[duckontheweb]

Yeah, I figured that was the reason.

It does seem like it would be good to have the maturity level reflect the current state, though. The transition from Proposal to Pilot seems to me to be more about going from an idea to an implementation (which has happened for this extension). I think it's okay that it's still a work in progress; that's why we still have the Candidate level prior to stabilizing.

That's just my opinion, though. I haven't been as intimately involved in the spec as others, so I'll defer to folks with a bit more experience. I'm only mentioning it because I'm referring to this repo in some exercises we're putting together and the maturity level didn't seem consistent with the descriptions in the Extension Maturity table. Given that things are going to change, I'm fine with leaving it as-is.