Hi Vitaliy,

I agree with you here. I don't think backwards compatibility is a compelling reason to keep the property-name-dictates-type feature. I don't believe there are that many wikis that have such a property defined without an associated type - and conversely, we know of a few wikis where this feature has caused problems, that have, for example, a property named "Telephone number" of type String or Text. I think it makes a lot of sense to just toss this feature out entirely - it will cause some short-term pain for a few admins, but in the long term it will simplify both the code base and the usage of SMW.


On Mon, Sep 23, 2013 at 10:14 AM, <vitalif@yourcmc.ru> wrote:

It seems the discussion in https://gerrit.wikimedia.org/r/#/c/84744/ is
slowed down, so maybe we'll discuss it here?

The full history is that I've recently discovered a strange SMW
behavior - type-named properties with enforced type. I.e. property named
"email" ALWAYS has email type, and you cannot override it. Markus said
it was done for some sort of backwards compatibility (details are in
gerrit), and I think it's an unevident behaviour, so I still think it
should be disabled...

To not break things with disabling this "feature" I suggest creating a
maintenance script (run as part of update.php) which will look for usage
of type-named properties and create them with [[has type::<name>]] if
they're really used.

What do you (SMW developers), and this mailing list subscribers in
general, think about it?

With best regards,
Vitaliy Filippov

LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
Semediawiki-devel mailing list

WikiWorks MediaWiki Consulting http://wikiworks.com