<<<
Chronological Index
>>> <<<
Thread Index
>>>
[gnso-contactinfo-pdp-wg] Wednesday 12 November 23:59 UTC soft deadline for comments
- To: "Dillon, Chris" <c.dillon@xxxxxxxxx>, "gnso-contactinfo-pdp-wg@xxxxxxxxx" <gnso-contactinfo-pdp-wg@xxxxxxxxx>
- Subject: [gnso-contactinfo-pdp-wg] Wednesday 12 November 23:59 UTC soft deadline for comments
- From: Emily Taylor <emily.taylor@xxxxxxxxxxxxx>
- Date: Wed, 12 Nov 2014 09:48:34 +0000
Dear Chris
I received one more input from the RrSG list on the draft document, as
follows:
One page 14, second bullet, there is a recommendation to have language tags
to allow easy identification of what the different data entries represent.
Here are the questions/comments that came up:
- EPP already supports the use of the localised form of the contact data as
well as the internationalised (ASCII) form of the contact data. Why does
the data need to be tagged with the language? What benefit is there? The
EPP RFC does not support passing anything other than the two forms of
contact data, meaning no ability to pass language or script tag
information, which adds non-essential complexity.
- If there is a compelling reason to tag all data elements, it should be
clearly articulated.
--
Emily Taylor
*MA(Cantab), MBA*
Director
*Netistrar Ltd *- Domain Names at Trade Prices
W: http://www.netistrar.com | M: 07540 049322 | T: 01283 617808
Repton House, Bretby Business Park, Bretby, Derbyshire, DE15 0YZ
Registered in England and Wales No. 08735583. VAT No. 190062332
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|