Recent
Newest approved public definitions for this language.
Automatischer Uebersetzungsentwurf (German) for "Definition Object Schema": The Definition Object Schema is a structured data definition that describes how definition object data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Definition Object Schema before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Definition Object Endpoint": The Definition Object Endpoint is a addressable API route that describes how definition object data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Definition Object Endpoint before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Canonical Term Contract": The Canonical Term Contract is a interface agreement that describes how canonical term data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Canonical Term Contract before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Canonical Term Response": The Canonical Term Response is a returned API object that describes how canonical term data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Canonical Term Response before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Canonical Term Payload": The Canonical Term Payload is a request or message body that describes how canonical term data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Canonical Term Payload before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Canonical Term Schema": The Canonical Term Schema is a structured data definition that describes how canonical term data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Canonical Term Schema before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Canonical Term Endpoint": The Canonical Term Endpoint is a addressable API route that describes how canonical term data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Canonical Term Endpoint before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Slug Contract": The Slug Contract is a interface agreement that describes how slug data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Slug Contract before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Slug Response": The Slug Response is a returned API object that describes how slug data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Slug Response before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Slug Payload": The Slug Payload is a request or message body that describes how slug data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Slug Payload before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Slug Schema": The Slug Schema is a structured data definition that describes how slug data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Slug Schema before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Slug Endpoint": The Slug Endpoint is a addressable API route that describes how slug data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Slug Endpoint before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Tag Filter Contract": The Tag Filter Contract is a interface agreement that describes how tag filter data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Tag Filter Contract before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Tag Filter Response": The Tag Filter Response is a returned API object that describes how tag filter data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Tag Filter Response before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Tag Filter Payload": The Tag Filter Payload is a request or message body that describes how tag filter data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Tag Filter Payload before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Tag Filter Schema": The Tag Filter Schema is a structured data definition that describes how tag filter data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Tag Filter Schema before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Tag Filter Endpoint": The Tag Filter Endpoint is a addressable API route that describes how tag filter data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Tag Filter Endpoint before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Locale Contract": The Locale Contract is a interface agreement that describes how locale data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Locale Contract before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Locale Response": The Locale Response is a returned API object that describes how locale data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Locale Response before sending article or definition data to PlatPhorm.”
Automatischer Uebersetzungsentwurf (German) for "Locale Payload": The Locale Payload is a request or message body that describes how locale data moves through PlatPhorm News APIs and feeds. It standardizes requests, responses, article listing metadata, and dictionary payloads for both humans and software agents.
“Beispielentwurf: The developer checked the Locale Payload before sending article or definition data to PlatPhorm.”