Hi everybody, and thanks for the help you have provided replying to my
last few queries.
I managed to achieve a good chunk of what I had in mind and I now have
a nice little infobox template (PersonBox) that includes another
template (Address), both of them adding semantic content without the
user having to worry about it.
So, the technicalities seems to have been sorted out. (*)
I was left however, with a bunch question marks concerning when and
how to use relations and when and how to use attributes. For example,
take my Address template, including fields such as office, floor,
buildingName, streetNumber, streetName, additionalLines (for the
address), city, county, country and postalCode. I could have added a
bunch of relations [[is located in::]], for example for the fields
buildingName, streetName, city, and county. But would that make sense?
I.e, if I then followed the link to a country, and assuming a
semantically populated wiki, I would then get a factbox with a
potentially long list of counties, cities and streets that are located
in that country. Alternatively, I could keep most fields as attributes
values, with only the streetName field creating a relation to the
city. This in turn is related to the county it's in and the county is
related to the country. Would that be a more appropriate way of doing
it, through a chain of relations? What would be the advantages and
disadvantages of this approach?
Thanks for your help!
(*) Except for the one problem that I mentioned in a previous email:
ask queries with a clause such as [[relation::*]] result in a blank
page. I have uncommented the ini_set() function and increased the
memory limit to 500M, but the result is the same. I still have to
activate MediaWiki debugging though.
vfx free electron
Get latest updates about Open Source Projects, Conferences and News.