Certainly. The spec says EITHER identfier or URL is required. If it IS an identifier, then that would mean it is an SPDX identifier and then you are free have the link refer to SPDX. But if identifier is not there, then that means it's a custom URL (e.g. to a URL on your own website's description of the license). In either case, the name (link text) should be simply the text one includes for the element. Important context is that SPDX does not have the concept of a commercial license. So for paid APIs that are "all rights reserved", the ability to describe the license fully by name is important. As far as backward compatibility, it seems to me only something that has an identifier might be a candidate for unilaterally adding the word license. But I would think even that's a stretch -- I'm not sure why, absent words in the 3.1 spec, one should be adding any words.

I imagine the name alleviates the need to query anything? The identifier IS the path to the SPDX license. I assume you're thinking about displaying the identifier, but there's currently only a single page element. So if you're thinking aboit adding that, then seems to me it's a separate div???