Browse-mode metadata includes information about the base table that the columns in the result set belong to.
For views created with VIEW_METADATA, the browse-mode metadata returns the view name and not the base table names when it describes columns from the view in the result set. If ALTER VIEW is not used, but instead the view is dropped and re-created, the previously used GRANT statement and any other statements that deal with permissions pertaining to this view must be re-entered.
Browse-mode metadata is additional metadata that the instance of Database Engine returns to the client-side DB-Library, ODBC, and OLE DB APIs.
This metadata enables the client-side APIs to implement updatable client-side cursors.
The view definition itself must first be modified or dropped to remove dependencies on the table to be modified.
WITH ENCRYPTION prevents the view from being published as part of SQL Server replication.
SCHEMABINDING Binds the view to the schema of the underlying table or tables.
Since the columns would come from a variety of tables, does this mean I can't run one blanket INSERT or UPDATE to persist changes in all the columns?
You can use an INSTEAD OF trigger on a view to keep your application only dealing with the view instead of the collection of base tables the view references.
However, we can add a unique, clustered index to a view, creating an indexed view, and realize potential and sometimes significant performance benefits, especially when performing complex aggregations and other calculations.