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 named value(s) to any page. I don't use Filters yet, so I can''t speak about them from experience. Category:Address & Concept:Address are poor practice - not plurals. Category:Addresses & Concept:Addresses have different functions. Categories list all pertinent wikipages; Concepts list specific wiki pages Type:Address - if there were such a thing -- is a singular notion. As in, Type:URL can be the datatype of Property:URL. Property:URL has default form::URL. Form:URL edits instances of Category:URLs.
Clutter can be reduced by eliminating optional Talkspaces. Clutter can be reduced by hiding unused namespaces where appropriate.. Combining namespaces = xxx:Address Form & xxx:Address Property. Yuck. And I store all addresses in their own namespace called Addr...! The 'proper number' of namespaces is in the eye of the beholder. It's a decision each wiki designer needs to make, no doubt. -----Original Message----- From: Robert Murphy [mailto:mrandmrsmur...@gmail.com] Sent: Friday, April 15, 2011 5:37 PM To: Smith, Tim Cc: semediawiki-devel@lists.sourceforge.net Subject: Re: [SMW-devel] Namespace Clutter OK, so then why are namespaces proliferating? On Fri, Apr 15, 2011 at 4:48 PM, Smith, Tim <smith.t...@pg.com> wrote: 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 [mailto:mrandmrsmur...@gmail.com] Sent: Friday, April 15, 2011 07:10 PM To: Jeroen De Dauw <jeroended...@gmail.com> Cc: Semantic MediaWiki Developers List <semediawiki-devel@lists.sourceforge.net> 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 <jeroended...@gmail.com> wrote: 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. 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. Cheers -- Jeroen De Dauw http://www.bn2vs.com 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. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel ------------------------------------------------------------------------------ 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. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel ------------------------------------------------------------------------------ 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. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
