Json Schema is too strict for current model.

[MadVikingGod]

Describe the bug
The schema currently produced by weaver is too restrictive for the current semantic convention model. When trying to validate a number of errors are shown, see gist

To Reproduce
Steps to reproduce the behavior:

Follow the behavior in the gist

Expected behavior
When validating with weaver schema the current model should pass. Similar to the current build tools schema:

$ yajsv -s build-tools-semconv.schema.json *.yaml 
url.yaml: pass
messaging-common.yaml: pass
session.yaml: pass
db-common.yaml: pass
general.yaml: pass
faas-common.yaml: pass
http-common.yaml: pass
network.yaml: pass

Additional context
The errors seem to be repeats of:

(root): registry_url is required
groups.0.attributes.0: brief is required
groups.0.attributes.0: name is required
groups.0.attributes.0: type is required
groups.0.attributes.0: Additional property ref is not allowed