On 25/09/11 05:18, Samuel Lampa wrote: > Sorry for repeating this, but wanted to remind about the need to update > the rest of the Architecture Overview article [1]. I guess that even > just updating the text that is there (there are two sections not updated > to 1.6) would go a long way? > > The problem now is that even parts supposed to be updated for 1.6 > changes still contain pointers to the supposedly ditched SMWDataValue > for example (see: [2]), which makes it somewhat confusing.
Indeed, I will see what I can do. > > I'd love to have a shortlist of the foundational classes I need to know > to represent triple data with SMW classes ... Should I basically be fine > with SMWDataItems (elements) and SMWSemanticData (aggregates of facts > per subject)? ... or is there some other foundational class I should add > to the shortlist? For representing input data, that's all. Query outputs are represented in SMWQueryResult (basically an iterator for a 3D-array) but the data returned there is also based on DIs. RDF data is represented by a smaller set of classes under SMWExpElement. These classes represent triples for the purpose of serialisation (they abstract RDF before fixing a concrete syntax such as RDF/XML or Turtle). Greetings (from the bus back to Oxford), Markus ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
