search

tracefirst / usaha_committee

XML schema for electronic CVIs
8 stars 2 forks source link

Need a signature element #30

Open nephiharvey opened 10 years ago

nephiharvey commented 10 years ago

We suggest adding a signature element like in the vet node and the origin node.

mkm1879 commented 10 years ago

Obviously the actual eCVI needs a signature and correct implementation of that is one big differentiating factor between implementations. Can you explain the need to transmit that as a data element outside the actual "legal document" version of the eCVI? The actual "legal document" is out of scope of this standard.

nephiharvey commented 10 years ago

Yes, but we have other non-necessry data in the standard that is being passed but not required for various reasons, so why not the signature. If the receiving party/DB does not want it, it can ignore it. But if it is pertanent, the standard should provide a way to send it. Otherwise, the first thing that will happen after the standard is written, is interested parties will break the standard by passing data (i.e. signatures as an example) that they need between them and then the standard is no longer adhered to. This is not a matter of legal document, it is however, pertinent data that may be needed between two interested parties. Thanks, and have a great Thanksgiving!

Nephi Harvey Chief Technology Officer Fort Supply Technologies, LLC Supplier of Animal Management Solutions

This email is Business Confidential and is intended for the addressed party only under the terms of any NDA that may be in place between the sending and receiving parties.

Fort Supply Technologies, LLC 1773 West 200 North Kaysville, Utah 84037

-or-

Fort Supply Livestock, Inc. Box 11 Robertson, Wyoming 82944

Email: nephi@fort-supply.com Fax: 801-991-9181 Phone: 801-726-1540 SKYPE: ntharvey01 iChat: ntharvey@mac.com WebSite: www.fort-supply.com

On Nov 27, 2013, at 2:12 PM, Michael Martin notifications@github.com wrote:

Obviously the actual eCVI needs a signature and correct implementation of that is one big differentiating factor between implementations. Can you explain the need to transmit that as a data element outside the actual "legal document" version of the eCVI? The actual "legal document" is out of scope of this standard.

— Reply to this email directly or view it on GitHub.

mkm1879 commented 10 years ago

I guess the issue comes in what you are calling a "signature." If you just mean a block of text or image that was attached visually, I guess you could do that. A real digital signature has a mathematical connection to the specific data that it covers and since the actual data will have been mapped to the exchange standard, the only way to include a digital signature that would make mathematical sense would be to include the entire signed data structure. Which you could obviously do at an attached file.

nephiharvey commented 10 years ago

I am not referring to a digital signature in the sense of an Adobe Digital Signature, but a image file, like a brand image, that is captured on screen of the signature of the owner and health inspector, more in the sense of a credit card signature. Just the image. That way the record of who signed is maintained. Thx.

Nephi Harvey Chief Technology Officer Fort Supply Technologies, LLC Supplier of Animal Management Solutions

This email is Business Confidential and is intended for the addressed party only under the terms of any NDA that may be in place between the sending and receiving parties.

Fort Supply Technologies, LLC 1773 West 200 North Kaysville, Utah 84037

-or-

Fort Supply Livestock, Inc. Box 11 Robertson, Wyoming 82944

Email: nephi@fort-supply.com Fax: 801-991-9181 Phone: 801-726-1540 SKYPE: ntharvey01 iChat: ntharvey@mac.com WebSite: www.fort-supply.com

On Nov 29, 2013, at 7:13 AM, Michael Martin notifications@github.com wrote:

I guess the issue comes in what you are calling a "signature." If you just mean a block of text or image that was attached visually, I guess you could do that. A real digital signature has a mathematical connection to the specific data that it covers and since the actual data will have been mapped to the exchange standard, the only way to include a digital signature that would make mathematical sense would be to include the entire signed data structure. Which you could obviously do at an attached file.

— Reply to this email directly or view it on GitHub.

mmcgrath commented 10 years ago

Nephi I'll add an optional element to contain the image as you have described. I'll call it "Signature Image" to avoid any confusion or interpretation that it is some type of cryptographic attribute.

Michael.

mmcgrath commented 7 years ago

On today's call, @mmcgrath proposed adding an enumeration to DocType called "Signature Image" which can accomodate @nephiharvey's request.