Semantic MediaWiki

Hi --

Is there any way to define a hierarchy of properties, even a shallow 
one, in Semantic MediaWiki?

I'm trying to create a wiki that maps out the space of semantic web 
technologies, including qualitative attributes about maturity, feature 
completeness, etc. I'd like to create a bunch of pages resenting 
semantic web or RDF datastores, as well as a bunch of pages resenting 
specific type of features (e.g. query language support, scalability, 
etc). I have found that simple yes/no tracking of features etc is too 
simplistic, and instead need another level of detail on the attributes. 
I'd like to use a simple hierarchy of qualifiers, for example:

   has_support_for_feature
       has_weak_support_for_feature
       has_average_support_for_feature
       has_strong_support_for_feature

With this in place I want to map features to implementations using RDF 
(or RDF-like) relations that use these properties and subproperties. 
Something like this:

ProjectA has_weak_support_for_feature SPARQL
ProjectA has_strong_support_for_feature ARQ
ProjectB has_support_for_feature SPARQL
ProjectC has_weak_support_for_feature some_other_query_language

I'd then like to be able to run a query to generate a list or table of 
all projects that support SPARQL, irrespective of how well they support 
it. That is, query for has_support_for_feature and have that match 
has_support_for_feature as well as any sub-property.

An alterate implementation would be to stick extra attributes on the 
property relations themselves, something like:

ProjectA has_support_for_feature SPARQL weak_support
ProjectA has_support_for_feature ARQ strong_support
ProjectB has_support_for_feature SPARQL
ProjectC has_support_for_feature some_other_query_language weak_support

This would work if the attributes could themselves be grouped into a 
hierarchy (i.e. weak_support and strong_support are subtypes of 
default_level_of_support). Either approach would work.

I've got this working with a non-semantic hack in Excel and a bunch of 
VBA scripts, but a wiki "feels" like a better match since most of the 
content is text based. However, the lack of metadata tracking and 
relationship mapping has stopped this migration so far. Is there any way 
to do this today with Semantic MediaWiki?

Thanks!

Ramon