Some WebDAV implementations seem to use displayName in their XML response instead of the more common displayname key.
<d:multistatus xmlns:d="DAV:" xmlns:oc="http://owncloud.org/ns" xmlns:nc="http://nextcloud.org/ns" xmlns:x1="http://open-collaboration-services.org/ns">
<d:response>
<d:href>/dav.php/@Home/new_library/</d:href>
<d:propstat>
<d:prop>
<d:displayName>new_library</d:displayName>
<d:getetag>80a1745cfaa43b2057f781413209ff90</d:getetag>
<d:getlastmodified>Tue, 22 Aug 2023 08:10:49 GMT</d:getlastmodified>
<d:creationdate>2023-08-22T10:10:49+02:00</d:creationdate>
<oc:id>02320738</oc:id>
<d:resourcetype>
<d:collection/>
</d:resourcetype>
<d:iscollection>1</d:iscollection>
<d:isFolder>t</d:isFolder>
<oc:permissions>RGDNVCK</oc:permissions>
<x1:share-permissions>31</x1:share-permissions>
</d:prop>
<d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
</d:response>
</d:multistatus>
Some WebDAV implementations seem to use
displayNamein their XML response instead of the more commondisplaynamekey.