Define how service types are named

[reinkrul]

Now we have NutsComm (in RFCs) and eOverdracht-receiver (and -sender) in the eOverdracht bolt.

We need to make this consistent and describe how service types must be named (e.g. nuts/.../... and bolt/.../...).

[reinkrul]

Suggestion

Service types;

• must be all lowercase.
• must start with nuts for types specified by the core specification (RFCs) or,
• must start with the Bolt name for types specified by Bolts (e.g. eoverdracht or zorginzage)
• Bolt names may contain a dash followed by a postfix (e.g. zorginzage-geboortezorg), which may appear any number of times.
• may have a postfix further describing the role of the service, which must follow after a forward slash (e.g. nuts/comm).

Examples:

• nuts/comm
• nuts/contactinfo
• eoverdracht/sender
• eoverdracht/receiver
• zorginzage-geboortezorg (without postfix)
• zorginzage-geboortezorg/custodian (with postfix specifying bronhouder service)

@stevenvegt @woutslakhorst ?

[woutslakhorst]

may have a postfix further describing the role of the service, which must follow after a forward slash (e.g. nuts/comm).
comm in this case would be the service type not the role.

It's very asymmetric: nuts services with a single / do not have a role but Bolt services do. It would be clearer then to use bolt/type/role

Also not sure on the hyphens (dashes are longer than hyphens)