Regarding the construction phases complex type that you want you have a couple of options. Properties support lists of values, so you could split the type into multiple properties and give a list of values for each. Then when qualifiers are added you could add a date range qualifier to each value to specify the phase or just use string qualifiers that say "phase 1", "phase 2", etc. depending on how detailed the information is. You can also group the properties in their own item. So you could create an item called "Potaissa phase 1 construction details" and then have construction phase just be a list of those specific items, which themselves contain the information.
Date: Wed, 27 Mar 2013 12:55:18 +0100
From: denny.vrandecic@wikimedia.de
To: wikidata-l@lists.wikimedia.org
Subject: Re: [Wikidata-l] A data model for Roman forts (castra)
I would say this is a good starting point. The Wikidata data model is described in full detail here [1], and a introductory primer is given here [2]. Qualifiers are not implemented yet, but will be there soon, and followed by more datatypes (like time, geo, etc.).
The major difference is that values like "stone" for material or "opus-quadratum" for technique should not be strings - this does not translate well. They should be pointing to items, e.g. Q8063 instead of "stone" and Q2631941 instead of "opus-quadratum".
The other thing is that Wikidata does not really intend to enable constraints in that very strong sense that your schema chooses. So if someone wants to add a value for material that you did not preconceive, like Q40861 (Marble), Wikidata-as-a-software will not stop them from doing so (just as Wikipedia-as-a-software does not stop you from entering that, either) (see also [3]).
I hope this helps,
Denny
_______________________________________________
Wikidata-l mailing list
Wikidata-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l