Background

These guidelines have been approved by the Use Cases Working Group in August of 2019.  They started as an 'opinionated' discussion document, followed by discussions, and then votes on what Use Cases (UC) the Working Group (WG) should accept. Having a set of agreed guidelines provides two benefits :

...

• reject a UC
• add the UC to their backlog
• indicate that the UC is already supported and show how the specification is used to deliver the UC.

But it is expected that the WG's will at least update the UC WG Confluence page with their decision and a brief 'reason'.

Please continue to engage with these Guidelines either by comments or by creating an alternative set of guidelines and referencing them in a comment on this page.

The Guidelines

In considering a use case, there are two separate questions to answer:

...

• Is it a real UC for FDC3 Personas?
• Does it apply to areas of concern for FDC3? Or areas which may require inclusion in FDC3 (e.g. Mobile to Desktop workflows)?
• Is it unique from other UCs?

...

In general a useful use case is one that will help solve interoperability issues found among members of FDC3 and will therefore, by definition, be a test case for the specifications being defined in other working groups.

Some specific questions to consider are :

...