Documentation/Repo cleanup

docs/define-your-own-telemetry-schema.md

@@ -36,8 +36,9 @@ dependencies:
 > - The `schema_base_url` field is not currently used by the weaver tool. It is
     intended for future use once telemetry schema v2 is fully specified and
     implemented.
-> - Only a single dependency at one level is supported. The most common use case
-    is depending on the OTEL semantic conventions registry.
+> - Weaver supports a maximum of 10 registry levels without circular
+    dependencies. In practice, this is not a limitation, even for complex
+    enterprise environments.
 
 Below is an example of a valid `registry_manifest.yaml` file:
 

docs/old-stuff/README.md

@@ -0,0 +1,4 @@
+# Outdated or obsolete content
+
+This directory contains documentation that is no longer up to date or requires
+significant updates. They are kept here for reference.

docs/component-telemetry-schema.md → docs/old-stuff/component-telemetry-schema.md

@@ -20,7 +20,7 @@ for more information).
 
 The following diagram shows how a Component Telemetry Schema is structured.
 
-![Telemetry Schema](./images/0240-otel-weaver-component-schema.svg)
+![Telemetry Schema](../images/0240-otel-weaver-component-schema.svg)
 
 > Note 1: Each signal definition, where possible, reuses the existing syntax and
 > semantics defined by the semantic conventions. Each signal definition is also

docs/resolved-telemetry-schema.md → docs/old-stuff/resolved-telemetry-schema.md

@@ -25,7 +25,7 @@ Telemetry Schema, 2) Resolved Telemetry Schemas serve as the mechanism for
 distributing Telemetry Schemas throughout the entire ecosystem, and 3) Resolved
 Telemetry Schemas would replace/augment existing SchemaURL.
 
-![Use cases](./images/0240-otel-weaver-use-cases.svg)
+![Use cases](../images/0240-otel-weaver-use-cases.svg)
 
 The main components of a Resolved Telemetry Schema are illustrated in the
 diagram below. The 'OTel Weaver' tool is used to create these schemas. It can
@@ -34,7 +34,7 @@ Resolved Telemetry Schema serves as a key mechanism for interoperability,
 feeding various external tools, including SDK generators, documentation
 generators, policy enforcers, and more.
 
-![Resolved Telemetry Schema](./images/0240-otel-weaver-resolved-schema.svg)
+![Resolved Telemetry Schema](../images/0240-otel-weaver-resolved-schema.svg)
 
 The internal catalog is used to define all the attributes and metrics in this
 artifact. This design allows for the reuse of the same attributes or metrics

docs/schema-changes.md

@@ -136,4 +136,4 @@ items (attributes, metrics, events, spans, resources). Future evolutions of the
 diffing process could generate a more detailed diff report by comparing the fields
 of those top-level schema items.
 
-This [document](schema-changes-explorations-for-future-evolutions.md) explores more complex uses cases.
+This [document](old-stuff/schema-changes-explorations-for-future-evolutions.md) explores more complex uses cases.