Hey,
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.
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 jeroended...@gmail.comwrote:
Hey,
You cannot put all the
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.
Tim
--
Sent using BlackBerry
From: Robert Murphy
Please dont collapse these into one namespace, or even two.
The *main issue* is *name conflicts*, secondarily user privledges.
There WOULD BE name conflicts between types, forms, properties filters.
Example:
Form:Address is used to edit the properties of an address.
Property:Address attaches
