WML and versions of HTML older than HTML 4 do not support the Link tag and so should not be used directly in resources written in those formats. However, Link tags can legitimately be written as HTTP response headers. This is discussed at length in the system specification document (see below) but requires you to configure your servers directly.
If you do not have access to your server configuration or simply find it easier to include the links to your labels in the content itself, there is a work around using the http-equiv meta tag. This allows you to write the equivalent of an HTTP response header as a meta tag.
The HTTP response header we want to create is:
Link: ; /=’/’; rel=’meta’ type=’application/rdf+xml’
is the actual link to the labels.rdf file in the server root. You will need to change this if you use a different file name or put it in a different location.
This HTTP Response Header can be encoded in an http-equiv meta tag thus:
This is valid HTML 3.2. In WML 2.0 you need to close the meta tag, either by adding a separate closing tag at the end or by using the (more usual for XML-based doctypes) / > empty tag construct.
Thanks to Andrew Darrow & Space.gs for their help with this issue.
Test data
You can see these tags in place in valid documents in the following formats: