Want to take part in these discussions? Sign in if you have an account, or apply for one below
Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.
Created elementary embedding to record a proof that I learned from Nate Ackermann. The upshot is that Kunen's technical argument for the inconsistency of an e.e. , and its use of choice, is unnecessary if you merely care about definable e.e.'s.
And created large cardinal as a stub, mostly so that elementary embedding wouldn't be an orphan.
The embeddings we used for Fraisse limits were only required to preserve and reflect the truth of atomic statements, rather than all first-order statements.
Couldn't hurt, I think.
I’ve formalized Urs’ observation from seven(!) years ago that an elementary embedding is a natural transformation, under Proposition 4.1. The following Remark 4.2 is closely related to Mike’s pullback condition: if you want a map between models to be compatible with the models’ interpretations of formulas in the theory, then the restriction (resp. pullback along ) of your map to the interpretation of a formula in should land in the subobject (resp. should come from ).
Thanks. I noticed that an entry “elementary embedding” was missing from model theory - contents and so I added it. In the course of this I rearranged slightly the list of keywords at the beginning, trying to put them more in logical order. Now it starts out like this:
…
I’m confused by this passage in elementary embedding:
More generally, when we consider structures in a category as in categorical logic, a morphism between structures in is an elementary embedding if for any formula , the following square is a pullback:
where denotes the object of interpreting the type , and denotes the corresponding subobject in interpreting the truth value of the formula .
One problem is that the types appear “out of the blue” - we start by saying “ between structures in is an elementary embedding if for any formula …”, and none of this mentions types . Can we add something to explain what they are, and what the are, and what the maps are? I’d do this myself if I could.
It seems that the are the types implicitly referred to earlier:
parameters (of appropriate types)
So this is typed first-order logic?
1 to 11 of 11