Fix link to ContentDirectory spec (#21985)

This commit is contained in:
Michael Chisholm 2022-03-12 21:00:27 +11:00 committed by GitHub
parent 3cf0cb178e
commit a92a2710aa
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -31,7 +31,7 @@ The `<media_identifier>` can have one of three forms:
- `path/to/file` or `/path/to/file`: Slash-separated path through the Content Directory. This must refer to a unique media item. - `path/to/file` or `/path/to/file`: Slash-separated path through the Content Directory. This must refer to a unique media item.
- `:ObjectID`: Colon followed by a server-assigned ID for an object. - `:ObjectID`: Colon followed by a server-assigned ID for an object.
- `?query`: Question mark followed by a query string to search for, see [DLNA ContentDirectory SearchCriteria](http://www.upnp.org/specs/av/UPnP-av-ContentDirectory-v1-Service.pdf) for the syntax. The first result found will be used. - `?query`: Question mark followed by a query string to search for, see [DLNA ContentDirectory SearchCriteria](https://openconnectivity.org/wp-content/uploads/2015/11/UPnP-av-ContentDirectory-v4-Service.pdf) (part 5.3.16 "A_ARG_TYPE_SearchCriteria" on page 65 and part D.5 "Searching" on page 269) for the syntax. The first result found will be used.
URIs generated while browsing will look like the Object ID form above. However, all three forms will work with the [media_player.play_media](/integrations/media_player/#service-media_playerplay_media) service. URIs generated while browsing will look like the Object ID form above. However, all three forms will work with the [media_player.play_media](/integrations/media_player/#service-media_playerplay_media) service.