Help:Type Record/Record vs. subobject

If you have a one to many relationship, then one of the two alternatives, preferably the  parser function, is going to be more appropriate, because you can query for them on one property, and retrieve the other properties (see examples below). Think of them as pages without having to have their own page and thus avoids cluttering up your wiki.

However, if you have a one to one (page to property value) relationship (enforced by form and template), then you could use either, but a record is going to be easier.

Parser function
See the help page Adding subobjects for a detailed description of this built-in alternative, which is available since.


 * Example "Semantic City"

It has several museums:

Where your museum template would set an subobject and display something too:

Now you can query for museums in a given city, and display their opening times:

As a result you should get the "Museum of Natural History" together with it's opening and closing times.CiteRef::sb:smw:semantic-city

Parser function
This alternative is provided by the but basically obsolete when using  or higher due to enhancements to parser function


 * Example "Semantic City"

It has several museums:

Where your museum template would set an internal object and display something too:

Now you can query for museums in a given city, and display their opening times:

As a result you should get the "Museum of Natural History" together with it's opening and closing times.