On Wed, 2011-10-19 at 13:32 +0100, Andy Seaborne wrote: > > >>> (1) try to model without using either one, when feasible > > which I took as also pushing RDF lists into the "not preferred > category". That's seems to be letting the technology influence the > modelling too much. > > The fact that an ordering construct is an RDF list which "has issues" > isn't the fault of the modeller. Right... What I was trying to get at here was the advice I often hear that modelers should not be using this kind of construct at all. Honestly, I'm very confused about this bit. Perhaps it's best addressed by having a little bit in the tutorial showing how something can be modeled with lists or without lists, and explaining the tradeoffs. -- SandroReceived on Wednesday, 19 October 2011 15:29:07 UTC
This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:02:01 UTC