So basically he's kind of threatening the expert witness now?
So basically he's kind of threatening the expert witness now?
It's unfortunately infrequently pursued when the perjury occurs in a civil case, but if you want to agitate for consequences, agitate for prosecutors willing to enforce the law.
(Or for a civil cause of action for perjury, but that would have to be carefully crafted to prevent an infinite regress of lawsuits.)
It probably isn't even perjury. Even the law has some room for interpretation. That is the whole point of case history. Technology is so new and fluid that the legal system may never catch up to or well define the things a crafty obfuscator (expert witness or lawyer) can sling out.
Skilled practitioners in the area of science or engineering will immediately identify the obfuscation and unreality of it, but that does not make it perjury, which does have a much more specific and well defined case law meaning.
Except that this is an "expert witness", and not a regular witness. The expert witness offers his/her opinions.
Certainly, an attorney can (and this is true of any witness, not just expert witness) coordinate with a witness on a line of questioning which carefully avoids any questions where perjury would be necessary to avoid damaging the case. That's why we have witnesses subject to examinstion by opposing counsel, as well.
It doesn't sound like Carmack was accusing the witness of lying, but rather they they believed a bit too much in their own pet theory about how to detect copying in code.
I don't usually like to comment on trials, but I think perhaps he has a point here. If there were a reliable method for detecting 'non-literal copying' of code, then the person who made it should be making a killing by selling refactoring tools.
Any time someone publishes a work, they are putting their reputation at risk. If the work is bad, the whole world will know they did it. Carmack is saying he thinks this should be the case for reports and analyses given by expert witnesses.
I don't think that makes sense. There is no attempt to generalize this to things people do in secret. There is no claim that if something could risk your reputation then it follows that it should be made public.
Carmack's assertion is only that this particular work (for which the witness does voluntarily and is paid for) should be made public so that these witnesses use the same level of rigor they would for their other published work. And letting the public review it would have benefits too. (I am not agreeing or disagreeing with this.)
Ultimately, if we take Carmack's statements as true, it sounds to me like Facebook/Occulus' defense did not do an adequate job of instilling doubt in the report. He wrote that the defense did a technical tear down. I think if I was a juror, I would need to see this report completely destroyed. I'd need to see the same methodology applied to works where we know there was no copying and have it find false positives.
I agree that in this specific instance, it was the job of Oculus' legal team to discredit the report in front of the court. Publishing it after the fact for review by the public doesn't make sense, and calling for it is petty.
Carmack isn't calling for it to be published. He only said he thinks the system should work that way.