A | B | C | D | E | F | G | H | |
---|---|---|---|---|---|---|---|---|
1 | Active membership of Open Energy | |||||||
2 | ||||||||
3 | Necessary conditions for active membership | |||||||
4 | An active member is an | Organisation | Not an individual | |||||
5 | That is able to | Request, receive, validate, and introspect, client-credentials M2M tokens signed by OE | ||||||
6 | Because they are | fully paid up at the time the token is requested | Note that tokens have lifetimes measured in seconds, so it's not the case that a member could, say, request a token, cancel, and continue to use it | |||||
7 | and because they have | accepted the OE membership contract | ||||||
8 | and because they have | provided evidence of an identifiable and authorised representative of the organisation to act as their organisation administrator - e.g. that data can be shared | ||||||
9 | and because they have | provided evidence of the facts about the organisation that we are prepared to assert, linked to the token we generate, about them | Such as "they're a charity", "they're a local authority", ... | |||||
10 | and because they have | renewed any such information as required by our policies | Some assertions we could make may be bound to time limited properties which require re-validation on a schedule | |||||
11 | ||||||||
12 | ||||||||
13 | Capabilities granted by active membership | |||||||
14 | An active data provider can | publish a valid metadata file describing their shared and open data sets | ||||||
15 | OE will automatically fetch and process metadata files for active members | Does this mean we actively drop info on data sets from lapsed/delinquent members? | ||||||
16 | ||||||||
17 | Active members can | request, receive, validate, and introspect OE-generated tokens | Core technical interactions with the Governance Service | |||||
18 | for data providers - receive assertions, with verified provenance, about a data consumer making a request | |||||||
19 | once they have | configured certificates generated by OE for MTLS | This provides basic technical access for both data providers and data consumers; such certs can have expiry dates that can be related to their membership contract | |||||
20 | ||||||||
21 | Active members can | request technical support | Within whatever parameters of support and response SLA we agree with them | |||||
22 | ||||||||
23 | Active members can | request non-technical support | Don't know what this would entail beyond routine membership status/admin tasks | |||||
24 | ||||||||
25 | Active members can | cancel their membership | ||||||
26 | ||||||||
27 | Active members can | administer their organisation details | Likely to be limited to adding and removing org administrators, and managing cryptographic material, but we can set the exact permissions | |||||
28 | ||||||||
29 | Active members can | <do the other things we define for their service level> | Catch-all sort-of use case so we can think through what other processes or tech might be needed in due course to provide membership service | |||||
30 | ||||||||
31 | ||||||||
32 | ||||||||
33 | ||||||||
34 | ||||||||
35 | ||||||||
36 | ||||||||
37 | ||||||||
38 | ||||||||
39 | ||||||||
40 | ||||||||
41 | ||||||||
42 | ||||||||
43 | ||||||||
44 | ||||||||
45 | ||||||||
46 | ||||||||
47 | ||||||||
48 | ||||||||
49 | ||||||||
50 | ||||||||
51 | ||||||||
52 | ||||||||
53 | ||||||||
54 | ||||||||
55 | ||||||||
56 | ||||||||
57 | ||||||||
58 | ||||||||
59 | ||||||||
60 | ||||||||
61 | ||||||||
62 | ||||||||
63 | ||||||||
64 | ||||||||
65 | ||||||||
66 | ||||||||
67 | ||||||||
68 | ||||||||
69 | ||||||||
70 | ||||||||
71 | ||||||||
72 | ||||||||
73 | ||||||||
74 | ||||||||
75 | ||||||||
76 | ||||||||
77 | ||||||||
78 | ||||||||
79 | ||||||||
80 | ||||||||
81 | ||||||||
82 | ||||||||
83 | ||||||||
84 | ||||||||
85 | ||||||||
86 | ||||||||
87 | ||||||||
88 | ||||||||
89 | ||||||||
90 | ||||||||
91 | ||||||||
92 | ||||||||
93 | ||||||||
94 | ||||||||
95 | ||||||||
96 | ||||||||
97 | ||||||||
98 | ||||||||
99 | ||||||||
100 |