Re: [ire] Extended verification process of the escrow deposit files

["Gould, James" <[e-mail]>]

Francisco,

Just to clarify the comment on CSV and XML.  The CSV format is defined in
XML and via XSD(s), so a validator (custom) would be able to verify the
CSV field formats of the CSV files in a similar fashion as using an XML
parser to validate an individual XML file against the XSD(s).  The email
address field value would be validated against the XSD simple element type
in either event.  
  
-- 

JG
 

 
James Gould
Principal Software Engineer
[e-mail]
 
703-948-3271 (Office)
12061 Bluemont Way
Reston, VA 20190
VerisignInc.com







On 12/17/12 4:00 PM, "Francisco Obispo" <[e-mail]> wrote:

>Hi *,
>
>On Dec 17, 2012, at 10:57 AM, "Gould, James" <[e-mail]> wrote:
>...
>> The Data Escrow Provider should be able to validate the completeness of
>>the deposit by verifying the signatures and verify the deposit against
>>the format definition.  Items like email address validation should be
>>covered by the XSD format definition.
>
>
>As long as we use the XML, if the CSV is used, the validation will have
>to proceed by type-checking the values in each file.
>
>>  Applying differential deposits to the full deposit also sounds like
>>the job of the EBERO provider and not the Data Escrow Provider.
>
>I agree,
>
>What I propose is to ICANN use its contracted EBEROs to validate and
>confirm that they can rebuild a registry with the information in the
>deposits. I would say at least two (selected at random).
>
>
>> In summary, I believe that only #1 below should be required of the Data
>>Escrow Provider and the remainder should be discussed as a requirement
>>for an EBERO provider.
>
>+1
>
>
>
>Francisco Obispo 
>Director of Applications and Services - ISC
>email: [e-mail]
>Phone: [phone] || INOC-DBA *3557* NOC
>PGP KeyID = B38DB1BE
>