- From: <bugzilla@jessica.w3.org>
- Date: Wed, 18 Jul 2012 18:00:53 +0000
- To: public-i18n-core@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18300
Summary: i18n-ISSUE-110: Contact information for meta
extensions registry
Product: HTML WG
Version: unspecified
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: minor
Priority: P2
Component: HTML5 spec
AssignedTo: dave.null@w3.org
ReportedBy: contributor@whatwg.org
QAContact: public-html-bugzilla@w3.org
CC: ian@hixie.ch, mike@w3.org,
public-html-wg-issue-tracking@w3.org,
public-html@w3.org, public-i18n-core@w3.org
This was was cloned from bug 16975 as part of operation convergence.
Originally filed: 2012-05-07 17:50:00 +0000
Original reporter: Addison Phillips <addison@lab126.com>
================================================================================
#0 Addison Phillips 2012-05-07 17:50:32 +0000
--------------------------------------------------------------------------------
Registered Extensions
http://wiki.whatwg.org/wiki/MetaExtensions#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.
================================================================================
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 18 July 2012 18:00:54 UTC