This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16975 - Registries: i18n-ISSUE-110: Contact information for meta extensions registry
Summary: Registries: i18n-ISSUE-110: Contact information for meta extensions registry
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other All
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
Whiteboard: registry
Depends on:
Reported: 2012-05-07 17:50 UTC by Addison Phillips
Modified: 2019-03-29 19:24 UTC (History)
8 users (show)

See Also:


Description Addison Phillips 2012-05-07 17:50:32 UTC
Registered Extensions

One of the registered extensions for the meta name attribute is dcterms.language ("A language of the resource. Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646].")

It would be nice to have a clear contact information for the person who submitted the proposed extension since I had to guess in order to send comments about dcterms.language.

There is also some text in the Synonyms column which I think is incorrect. It is not clear to me who wrote that, and I'd like to talk with them because I think it is possibly incorrect/misleading.

So I'd like to see:
1. a column to indicate an email/contact address for the submitter of a proposal
2. guidelines that people editing the columns should provide contact information when they do.
Comment 1 contributor 2012-07-18 18:00:56 UTC
This bug was cloned to create bug 18300 as part of operation convergence.
Comment 2 Ian 'Hixie' Hickson 2012-07-25 03:07:47 UTC
Will revisit this after we rework how registries are done.
Comment 3 Ian 'Hixie' Hickson 2012-10-02 19:29:12 UTC
Marking LATER as I'm not planning on doing the registry revamp in the near future. Will get back to this.
Comment 4 Domenic Denicola 2019-03-29 19:24:21 UTC
Nobody has an appetite for a new registry system, as flawed as the current one may be, so we'll close this constellation of bugs for now. If folks want to continue discussing the issues with the IANA and meta registries, is the place.