Template talk:Concept relation

Type Annotation URI cannot have #. What should we do? --Andreas Plank 00:23, 20 September 2012 (CEST)

Relations always as [[Has type::Annotation URI]] or as [[Has type::Page]]?

[[Has type::String]] is definitely not the best SMW-Has type for all relations. I suppose it should be set URI-something, to [[Has type::Annotation URI]] or set it to page and save additionaly special property:Equivalent URI? --Andreas Plank 14:48, 10 October 2012 (CEST)

Should be of type [[Has type::Page]] Andreas Plank 17:29, 11 October 2012 (CEST)

Property vs. subobject approach

DRAFT: Using subobjects to display property settings made on a concept page it may be confusing to see subobject identifier in the Property browser that link to the whole page instead to a specific identifier on a concept page. Two different approches are compared below:

Try to find a good solution also for RDF export

Property approach	Subobject approach
#ask and iterate over all global relations (defined on property pages) step through each relation: check: #ask (this-relation-is-on-concept-{{PAGENAME}}) resolve display text/property maintain: property parameter on property pages manage what relations are evaluated list of relations in Template:Concept relation/relation to property (to get form-selection to property-code) list of relations in Form:Concept …?	#ask and iterate over relations related to a specific concept page iterate over former ask result together with "format=template" to display results maintain: list of relations in Template:Concept relation/relation to property (to get form-selection to property-code) list of relations in Form:Concept …?
(+) save relation data not twice (–) rewrite code (–) needs additional work around to count, filter data from a page (not possible with #ask directly)	(+) #ask can be used to count, filter directly and correctly (–) confusing browsable data links with IDs that do not resolve to (HTML IDs, RDF): Extension:Semantic Internal Objects might be better suited for this (has no confusing browsable data objects (–/+) data are stored twice in most circumstances