On Freitag, 7. Dezember 2018 21:30:43 CET Tedd Sterr wrote: > Having the Compliance Suites in an XEP feels somewhat out of place to me - > an XEP listing other XEPs (I know many XEPs refer to others, but it's not > the same.)
> Would it be better to run it as a separate set of documents - > XMPP Compliance Suites (XCS)? I agree, somewhat; having this as a XEP is, semantically, not really sensible because it is not an extension proposal in itself, but rather a list of extensions which might be useful to have. I wouldn’t go so far to make it a separate track of documents. Maybe it would be sufficient to have a separate section on the xmpp.org website where one has the current compliance suite as home page and the older revisions on the sidebar. It could be linked from the main menu, making it extremely discoverable. However, I’m not super-convinced we can get this done in this time frame and I have to admit that I’m at fault here, because I promised to do this in time. > This would have the benefit of making them > more disocverable, rather than getting lost in the XEPs list (it took far > too long before I even discovered the Compliance Suites existed.) They > could be numbered by year, and the latest would be obvious: XCS-2019. kind regards, Jonas _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
