can't have an n-ary relation composed of an enumerated type
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	• bzimport
	Sep 20 2007, 8:55 PM

Description

Author: info

Description:
In SMW 1.0pre-alpha3 a property can have multiple types. But if one of those is Enumeration, the property doesn't work. The factbox always complains "Possible values for this property are not enumerated."

Even if a compound property could find special properties of its component types on its page, how would SMW know the component type to which they apply? E.g. Property:Bug might have an enumerated severity and enumerated priority; where would you specify the two separate lists of "allows value".

I suspect similar problems with trying to specify primary units and desired formats of component types of n-ary relations.

For what it's worth Yaron Koren identified other issues with the current design in http://sourceforge.net/mailarchive/message.php?msg_name=55dbda5c0709102237n535a4a36ia0798029197441a7%40mail.gmail.com

Version: unspecified
Severity: minor
URL: http://ontoworld.org/wiki/Property:Bug

Details

Reference: bz11411

Event Timeline

• bzimport raised the priority of this task from to Medium.Nov 21 2014, 9:57 PM

• bzimport added a project: MediaWiki-extensions-Semantic-MediaWiki.

• bzimport set Reference to bz11411.

• bzimport created this task.Sep 20 2007, 8:55 PM

Nary properties will not support all features of normal properties yet. It is planned to revisit earlier design decisions regarding some property settings, and to make naries compatible with the emerging design. Probably SMW1.0 will ship naries as "experimental".

We now have datatype Record since SMW 1.5.0 Thus closing this as RESOLVED FIXED.

can't have an n-ary relation composed of an enumerated typeClosed, ResolvedPublicActions

Description

Details

Event Timeline

can't have an n-ary relation composed of an enumerated type
Closed, ResolvedPublic
Actions