# CSDM Example Series: Platforms

- Title: CSDM Example Series: Platforms
- Video URL: https://www.youtube.com/watch?v=-wD-E5IBzys
- Playlist position: 60
- Frameworks discussed: CSDM
- Evidence basis: YouTube MCP playlist metadata and title only; transcript retrieval failed in this session.

## Short summary
Title indicates a concrete CSDM modeling pattern discussion, likely covering how to classify or relate services, APIs, microservices, platforms, or lifecycle states.

## Key mapping concepts
- Precise class placement instead of loose semantic overlap
- Service, application, API, and platform boundary discipline
- Relationship patterns that support later impact analysis

## Notable terminology used
- CSDM

## What still seems valid
The insistence on precise class boundaries still looks valid because ontology quality depends on disciplined distinctions between product, service, application, API, and platform concepts.

## What appears outdated or version-specific
No explicit transcript evidence was available, so only obvious title-level versioning can be called out with confidence.

## Transcript
Transcript retrieval was not available from the YouTube MCP server in this session. Direct `youtube_get_transcript` calls returned `401`, and a bulk playlist transcript request returned `0` items on 2026-03-26.

## Relevance to current ontology work
Medium to high relevance. Concrete modeling debates help define the precise boundaries that a durable ontology needs, particularly around service/application/API/platform distinctions.

