The related_applications member of this specification currently only has a single implementation. As such, it has been marked "at risk" as per the W3C Process, meaning that:
[The feature] may be removed before advancement to Proposed Recommendation without a requirement to publish a new Candidate Recommendation.
The Web Apps Working Group is seeking a second implementation in order to keep this feature in the specification.
The text was updated successfully, but these errors were encountered:
Why is there resistance to implementation. It would seem natural for a progressive/micro-service weighted platform to encourage if not insist on loose coupling of related apps.
The
related_applications
member of this specification currently only has a single implementation. As such, it has been marked "at risk" as per the W3C Process, meaning that:The Web Apps Working Group is seeking a second implementation in order to keep this feature in the specification.
The text was updated successfully, but these errors were encountered: