Change Details

PLACEHOLDER @WMDE-leszek GET /entities/items/{item_id}/labels/{language_code} GET /entities/items/{item_id}/descriptions/{language_code} GET /entities/items/{item_id}/aliases/{language_code} The respective successful responses should present the relevant data as a string, or array of strings in case of aliases -- similar to the response structure of GET /entities/items/{item_id} Cases to consider: - if {item_id} is a redirect, the API should generate a 308 response redirecting to a respective path on the redirect target - if {item_id} does not exist, the API should generate a 404 response `{ "code": "item-not-found", "message": "Could not find an item with the ID: {item_id}" }` - if {item_id} is not a valid item ID, the API should generate a 400 response `{ "code": "invalid-item-id", "message": "Not a valid item ID: {item_id}"} ` - if {language_code} is not a valid language code, the API should generate a 400 response `{ "code": "invalid-language-code", "message": "Not a valid language code: {language_code}"} ` - if given item does not have a label, description, or any alias in the give the API should generate a 404 response `{ "code": "label|description|alias-not-defined", "message": "Item with the ID {item_id} does not have a label/description/an alias in the language: {language_code}" }`

PLACEHOLDER @WMDE-leszek GET /entities/items/{item_id}/labels/{language_code} GET /entities/items/{item_id}/descriptions/{language_code} GET /entities/items/{item_id}/aliases/{language_code} The respective successful responses should present the relevant data as a string, or array of strings in case of aliases -- similar to the response structure of GET /entities/items/{item_id} Cases to consider: - if {item_id} is a redirect, the API should generate a 308 response redirecting to a respective path on the redirect target - if {item_id} does not exist, the API should generate a 404 response `{ "code": "item-not-found", "message": "Could not find an item with the ID: {item_id}" }` - if {item_id} is not a valid item ID, the API should generate a 400 response `{ "code": "invalid-item-id", "message": "Not a valid item ID: {item_id}"} ` - if {language_code} is not a valid language code, the API should generate a 400 response `{ "code": "invalid-language-code", "message": "Not a valid language code: {language_code}"} ` - if given item does not have a label, description, or any alias in the give the API should generate a 404 response `{ "code": "label|description|alias-not-defined", "message": "Item with the ID {item_id} does not have a label/description/an alias in the language: {language_code}" }` Note: At this point, no language fallback is to be considered.

PLACEHOLDER @WMDE-leszek GET /entities/items/{item_id}/labels/{language_code} GET /entities/items/{item_id}/descriptions/{language_code} GET /entities/items/{item_id}/aliases/{language_code} The respective successful responses should present the relevant data as a string, or array of strings in case of aliases -- similar to the response structure of GET /entities/items/{item_id} Cases to consider: - if {item_id} is a redirect, the API should generate a 308 response redirecting to a respective path on the redirect target - if {item_id} does not exist, the API should generate a 404 response `{ "code": "item-not-found", "message": "Could not find an item with the ID: {item_id}" }` - if {item_id} is not a valid item ID, the API should generate a 400 response `{ "code": "invalid-item-id", "message": "Not a valid item ID: {item_id}"} ` - if {language_code} is not a valid language code, the API should generate a 400 response `{ "code": "invalid-language-code", "message": "Not a valid language code: {language_code}"} ` - if given item does not have a label, description, or any alias in the give the API should generate a 404 response `{ "code": "label|description|alias-not-defined", "message": "Item with the ID {item_id} does not have a label/description/an alias in the language: {language_code}" }` Note: At this point, no language fallback is to be considered.