I'm pretty sure they can't claim they get to enforce what they intended to write just because I happened to guess what that was by Googling parts of my contract. What I signed is what I signed, and the wording was clear in the contract.
I'm pretty sure they can't claim they get to enforce what they intended to write just because I happened to guess what that was by Googling parts of my contract. What I signed is what I signed, and the wording was clear in the contract.
If a contract is written as:
You own things you make on your own time unless you're using company equipment provided: * The thing does not relate to company business * The thing does not result from work you do for the company
It's pretty clear cut what this means and a judge would not care for boolean logic. Of course it's hard to know for sure without knowing the exact wording of the contract.
In fact, what would be weird would be someone objecting to my bringing both on the grounds that they meant, but didn't say, "xor".
I don't think this contract is ambiguous in natural language. Or is generally inclusive, and if you want xor you either write xor or use some cumbersome circumlocution.
Logical OR is often written as ‘and or’. Do you want to see a movie and or get dinner? https://en.m.wikipedia.org/wiki/And/or
That said it’s not a universal standard and like most of English has wide regional differences.
I would say OR is the natural use, and exclusion is implied by the context in these examples.
While "on your own time" and "using company equipment" are reasonably clear concepts, the other two clauses are too debatable to be an acceptable risk. It's not a matter of Boolean logic.