https://bugzilla.wikimedia.org/show_bug.cgi?id=31063
--- Comment #24 from Daniel Friesen <mediawiki-b...@nadir-seen-fire.com> 2011-11-23 08:35:29 UTC --- (In reply to comment #23) > > No, that's not "today's standard system", that's the verbose XML cult of > > thought. > > You mean the Internet and the Semantic Web (including other serializations > than > xml) is a cult? :-) > > > Extension authors should have no reason to need to type in a full long uri > > every time they refer to a namespace. > > Absolutely no need, they would use a local variable name. Extensions shouldn't need to store something like that in a variable. And they WILL need to use it in multiple places in an extension so they WILL have to write it out multiple times. And the moment they store it into a SMW_PROPERTY like constant all of the extra value of that full uri practically disappears. > > Not to mention how decision on renaming extension pages or switching to a > > different system for extension management could affect something that should > > not be dependent on them. > > I don't understand the above. Say our extension is located at "http://www.mediawiki.org/wiki/Extension:SemanticMediaWiki"; and we decide to use the url as the property: "http://www.mediawiki.org/wiki/Extension:SemanticMediaWiki#Property"; But say we later decide to move "SemanticMediaWiki" to "Semantic MediaWiki". Now the url we're using isn't actually the url that the extension uses. And we can't change that, because that's what we use as a unique identifier and if we change it MW will try to create a new namespace and make all our current content disappear. Likewise say we ditch the Extension: namespace and switch to some sort of dedicated system that has a special interface for managing extensions, versions, releases, etc... and say we use http://extensions.mediawiki.org/ for that. Now all the urls used in extensions are either incorrect or things break. Decisions like these shouldn't have an effect on something like the identifier used for an extension namespace. > > My assumption is that extensions need globally unique identifiers. Else you > either have to create yet another global registry, or two extensions end up > using the same identifier. Traditionally many domain specific registries > existed, but I stand by my comment: increasingly we do switch these to URIs, > whether it is photometadata, institutions, publications, authors, biological > organism names, etc. It is not strictly a "standard system" - please excuse my > lax use of language. But it is not a cult, it is a well reasoned, sane > decision. Except we don't need unique identifier at the level of a url. In fact if we're going by the extension's MW.org page then of the identifier "http://www.mediawiki.org/wiki/Extension:SemanticMediaWiki#Property"; the entire "http://www.mediawiki.org/wiki/Extension:"; portion of that identifier is worthless. Quite frankly "smw.*" or maybe "ext.smw.*" is enough specificity for our purposes. Do remember that these keys we're using all just map to very non-unique things like "Property:", "Thread:", "Video:", etc... That level of non-uniqueness is not going away, and all we need on top of that for keys is a little differentiation between different extensions, core, and site namespaces. And for those purposes the extension name is enough (and for well known extensions like Semantic MediaWiki short keys like smw are even enough). We haven't had an issue with conflicts. And DPL Wikimedia vs. DPL2 isn't a conflict, we'd probably 'want' those to use the same namespace. And there may be other cases where there's a reason for extensions to share a namespace key. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
