Support for wildcards in pub/sub topics?

[hspaay]

What content needs to be created or modified?

Many message bus systems, eg mqtt, amqp, etc, have support for wildcards in their topics. The dapr pub/sub documentation only shows topics as a single verb and does not mention the use of wildcards or characters such as '.' and '/'. This leaves one wondering what is in-scope and what is out-of-scope for topic definitions and what the intended purpose of dapr pub/sub is.

Describe the solution you'd like

Ideally the topic definition clearly states the accepted semantics for topics, including the use of wildcards and special characters. In addition, some use-cases that show what is in-scope and out-of-scope. The orders example is more basic than most people with have to deal with. Do the pub/sub features cover a more complex use-case? For example, an IoT device might want to publish a topic 'things/{thingID}/event/{eventName}', while subscribers to Thing events handle this topic with a wildcard for thingID and eventName. Is this usage out of scope?

Where should the new material be placed?

Possible location: https://docs.dapr.io/developing-applications/building-blocks/pubsub/

The associated pull request from dapr/dapr, dapr/components-contrib, or other Dapr code repos

Additional context