On 3 October 2011 16:48, Markus Krötzsch <mar...@semantic-mediawiki.org> wrote: > On 03/10/11 10:50, Dan Bolser wrote: > ... >> >> Thanks Markus, >> >> Perhaps a very dumb question, but what advantages are there to using >> subobjects over real pages? >> >> i.e. When is it recommended to use a subobject over a regular page? >> (That is, disregarding peoples sensibilities over 'too many' or >> 'messy' pages, which are purely subjective). >> >> Currently, the main reason I use SIO is because they work so nicely >> with multi-instance templates in SF, but this is a SF limitation >> rather than a decision driven by 'data design' or modelling >> considerations. (One form can only edit one page at a time). >> >> Probably this was discussed at SMWCon, but if there is no other >> permanent record you can point me at, it would be great if you could >> put the key points here. > > There was not too much of a discussion about the general motivation. > Subobjects are really just like pages as far as the structure of the stored > data is concerned. However, there really are cases where the creation of a > page would seem inappropriate, e.g., when the subobject merely groups two > values. For example, you would not want pages for "300g butter or > margarine". In other cases, the policy of the wiki might be to not have > individual pages for some item, even if it could be argued for as an > individual subject (like my address example). Subobjects let you handle such > situations in a more flexible way.
I definately see the advantage when it comes to linking specific quantities with types, as quantities are infinitely variable, you wouldn't wan't a page for every specific permutation. Now I'm thinking about having [[butter::600g]] ... I guess it's good to have more than one way to do things. Overall it does 'feel tidier' to have a simple set of content pages rather than many arbitrary 'data pages', but I'm just looking for a way to quantify it. (After all, users are likely to stick to content pages if that is where your site design keeps them). I guess two suggested guidelines come to mind: 1) The subobject should be strictly dependent on its parent object, i.e. it only makes sense to store the data for that subobject on the parent page, and the data shouldn't be duplicated elsewhere (very often). 2) There should never be a need to add free text or otherwise discuss the subobject separately from the parent page (which stems from point 1 I guess). Cheers, Dan. > Regards, > > Markus > > > ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
