client output not what i expect. no resourceSpan

[data-dude]

If you look at the links below - opentelemetry spec and quickwit - you see the format is resourceSpans and then the info but the output for the python client is not in that format. Does anyone know why the Python client is not using the resourceSpans tag? My Jaeger collector will accept resourceSpans input but not the python client input.

https://github.com/open-telemetry/opentelemetry-proto/blob/main/examples/trace.json

https://quickwit.io/docs/main-branch/distributed-tracing/send-traces/using-otel-collector

source code:
https://github.com/open-telemetry/opentelemetry-collector/blob/v0.141.0/pdata/ptrace/generated_resourcespans.go

i believe correct format:

{
  "resourceSpans": [
    {
      "resource": {
        "attributes": [
          {
            "key": "service.name",
            "value": {
              "stringValue": "my.service"
            }
          }
        ]
      },

incorrect? format using python library:

{
    "name": "child-span-2",
    "context": {
        "trace_id": "0x234da7e192d66aa4d3e70bc822df5c4a",
        "span_id": "0xf48c9eb785ea361b",
        "trace_state": "[]"
    },
    "kind": "SpanKind.INTERNAL",
    "parent_id": "0x551ba21238d6e37e",
    "start_time": "2025-12-15T15:28:18.736022Z",
    "end_time": "2025-12-15T15:28:18.736030Z",
    "status": {
        "status_code": "UNSET"
    },
    "attributes": {},
    "events": [],
    "links": [],
    "resource": {
        "attributes": {
            "telemetry.sdk.language": "python",
            "telemetry.sdk.name": "opentelemetry",
            "telemetry.sdk.version": "1.39.1",
            "service.name": "my-python-app"
        },
        "schema_url": ""
    }
}

python code:

# batch_span_console_example.py

from opentelemetry import trace
from opentelemetry.sdk.resources import Resource
from opentelemetry.sdk.trace import TracerProvider
from opentelemetry.sdk.trace.export import (
    BatchSpanProcessor,
    ConsoleSpanExporter,
)

# 1. Acquire a resource (optional but recommended)
#    A resource represents the entity producing the telemetry (e.g., your service name).
resource = Resource.create(
    {"service.name": "my-python-app"}
)

# 2. Create a TracerProvider
provider = TracerProvider(resource=resource)

# 3. Create a ConsoleSpanExporter
#    This exporter prints spans to the console.
console_exporter = ConsoleSpanExporter()

# 4. Create a BatchSpanProcessor and add it to the provider
#    This processor buffers spans and exports them in batches, which is efficient for production use.
provider.add_span_processor(BatchSpanProcessor(console_exporter))

# 5. Set the global tracer provider
trace.set_tracer_provider(provider)

# 6. Get a tracer and create spans
tracer = trace.get_tracer(__name__)

with tracer.start_as_current_span("main-operation"):
    print("Performing some work with traces...")
    with tracer.start_as_current_span("child-span-1"):
        print("Inside child span 1...")
    with tracer.start_as_current_span("child-span-2"):
        print("Inside child span 2...")

print("Traces have been generated and will be exported to the console.")

[data-dude]

closing. maybe i don't understand the spec