Being a member of a namespace does not imply that a resource is a specific rdf:type (i.e. Property, Class, etc...). The rdf:type property should be used to ascertain the type of a resource.


Sent using BlackBerry

From: Robert Murphy []
Sent: Friday, April 15, 2011 07:10 PM
To: Jeroen De Dauw <>
Cc: Semantic MediaWiki Developers List <>
Subject: Re: [SMW-devel] Namespace Clutter
OK, 2 namespaces: fundamentals and derived things.  TYPE's are not defined in terms of anything else.  Property's, Form's, Filter's and Concept's all have definitions written on them..

On Fri, Apr 15, 2011 at 4:02 PM, Jeroen De Dauw <> wrote:

You cannot put all the stuff in one namespace; how would you then know what it actually is? For example properties show a list of pages on which they are used (plus the value they have there). This information would need to be represented in another way if it all was in a single namespace. The current approach makes it very obvious what the thing is, a property, type or something else. Also, it avoids naming conflicts. I honestly don't see why you'd put everything in a single ns, it seems it'd only cause issues and not provide any benefits.


Jeroen De Dauw
Don't panic. Don't be evil.

Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization.
Semediawiki-devel mailing list