I'm not sure if my view on this is unusual, but I think it's worth noting the value of the RDFS and OWL vocabularies as expressive ways to describe the expected shape of data. This information can be used in all sorts of ways short of reasoning. Specifically, I use OWL and RDFS all the time to:
- Drive user interfaces
- Provide auto-complete capabilities
- Auto-generate forms, facets, ...
- Guide input (e.g. pick lists based on owl:oneOf constructs)
- Drive client-side validation (yes, this assumes a closed world)
- Drive server-side validation / integrity constraint checking (yes, this assumes a closed world)
I'm sure there's more, too. But the overall point is that these vocabularies are extremely useful (way more useful than things like XML Schema in my opinion) for simply describing data and relationships.
The fact that in many circumstances I can use these very same schemas and ontologies to reason over my data and derive new data and new classifications that can further simplify users' experiences is simply gravy for me.
Lee
PS I should add that rules is a different beast for me. I think rules are incredibly useful, though sometimes opaque to create. I haven't thought a lot about how they interact with The Semantic Web (Linked Data Web), but in general I think the best path forward for rules (& reasoning) is often to make it a "local thing" that happens in the context of a particular application.