Area(s)
area:url
What's the problem?
The url.subdomain attribute is defined with the following brief:
The subdomain portion of a fully qualified domain name includes all of the names except the hostname under the registered_domain. In a partially qualified domain, or if the qualification level of the full name cannot be determined, subdomain contains all of the names below the registered domain.
(Emphasis mine.)
The note says:
The subdomain portion of www.east.mydomain.co.uk is east. If the domain has multiple levels of subdomain, such as sub2.sub1.example.com, the subdomain field should contain sub2.sub1, with no trailing period.
(Emphasis again mine.)
I can't figure out by what rule or guideline the www label of the www.east.mydomain.co.uk domain name would be excluded from the subdomain. www.east precedes the registered domain in the same way that sub2.sub1 does in the following example - the brief seems fairly explicit that www.east would be the expected value. There is no mention of special handling for www labels here or elsewhere in the url model.
Describe the solution you'd like
In order of preference, my suggested solutions are:
- Update the expected
url.subdomain of www.east.mydomain.co.uk to www.east. IMO the existing definition as written for url.subdomain is sensible, and we should follow it.
- Update
url.subdomain's brief to specify why the leading www. is not part of www.east.mydomain.co.uk's subdomain. If this example is truly intentional, then it ought to be part of the field's specification.
It appears that this definition and example was imported from ECS in #496, if that's a consideration.
Tip
No response
Area(s)
area:url
What's the problem?
The
url.subdomainattribute is defined with the following brief:(Emphasis mine.)
The note says:
(Emphasis again mine.)
I can't figure out by what rule or guideline the
wwwlabel of thewww.east.mydomain.co.ukdomain name would be excluded from the subdomain.www.eastprecedes the registered domain in the same way thatsub2.sub1does in the following example - the brief seems fairly explicit thatwww.eastwould be the expected value. There is no mention of special handling forwwwlabels here or elsewhere in theurlmodel.Describe the solution you'd like
In order of preference, my suggested solutions are:
url.subdomainofwww.east.mydomain.co.uktowww.east. IMO the existing definition as written forurl.subdomainis sensible, and we should follow it.url.subdomain's brief to specify why the leadingwww.is not part ofwww.east.mydomain.co.uk's subdomain. If this example is truly intentional, then it ought to be part of the field's specification.It appears that this definition and example was imported from ECS in #496, if that's a consideration.
Tip
No response