As a language, PowerShell is full of interesting powers. One of the less understood, but more powerful, ones is the view system.
In PowerShell, you're constantly running into different types of data, so how you're exposed to this information means a lot.
Because of this, there is a very flexible types and formatting system in PowerShell.
You can define a view for any type of object, and, by default, PowerShell will show you every property that object has.
Pipeworks works the same way: You can let it display a table of properties on an object, or you can declare a view.
Also, just like PowerShell ships with views for types you're going to see a lot (like WMI classes or performance counters), Pipeworks ships with a lot of views for the types of objects you'll find on the web.
It can do this on the backs of Schema.org
and the sister site we run: ShouldBeOnSchema.org
These sites keep common lists of property bags you can use, and the most common of these property bags are views included with Pipeworks.