If I understand what you are trying to accomplish, then I would say “most definitely yes”. The context represents a logical chunk of functionality in your application - something that your application knows how to do. Say your application was for tracking shipments, then your context would be about how do you represent a shipment, what kind of operations can you do on shipments etc.

Your schema sits at the edge of your application and is concerned with how the elements of the context are represented in one particular type of storage (that being stored in a database). It’s a separation of concerns issue; you’re trying to separate what a thing is, from how that thing happens to be stored. If you wanted to get rid of a database and use a flat-file, or hook your application up to a 3D printer that generated plastic slabs where the data is encoded as if chiseled in stone, then you wouldn’t need the schemas - but the main logic of your application, the contexts, should still be valid.