II.
Domain JSON
Structured · livedomain:telecommunications
Telecommunications json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "domain:telecommunications",
"_kind": "Domain",
"_file": "domain/domains/social-humanities-domains.yaml",
"_cluster": "domain",
"attributes": {
"displayName": "Telecommunications",
"description": "Telecom infrastructure, 5G, spectrum management, and network operations.\n"
},
"outgoingEdges": [
{
"from": "domain:telecommunications",
"to": "specialization:network-programming",
"kind": "contains"
},
{
"from": "domain:telecommunications",
"to": "specialization:electrical-engineering",
"kind": "contains"
}
],
"incomingEdges": [
{
"from": "language:erlang",
"to": "domain:telecommunications",
"kind": "applies_to",
"attributes": {}
},
{
"from": "specialization:telecommunications-engineering",
"to": "domain:telecommunications",
"kind": "specializes"
},
{
"from": "stack-profile:erlang-otp-telecom",
"to": "domain:telecommunications",
"kind": "applies_to"
},
{
"from": "workflow:network-capacity-planning",
"to": "domain:telecommunications",
"kind": "applies_to_domain",
"attributes": {}
},
{
"from": "workflow:spectrum-allocation-review",
"to": "domain:telecommunications",
"kind": "applies_to_domain",
"attributes": {}
}
]
}