Hi @Smag0, the brackets are RDF lists, which are somewhat cumbersome, and for which Tripledoc does not have convenience methods to make them easier to work with. (The same holds true for BlankNodes, which it uses behind the scenes.) I found this post, the introduction of which explains how lists are implemented: http://www.snee.com/bobdc.blog/2014/04/rdf-lists-and-sparql.html
You can simulate them in Tripledoc by recreating its data structure, using regular TripleSubjects instead of BlankNodes. Off the top of my head, that would look something like this:
As for XML:color - unfortunately Tripledoc does not have an addColor method yet (contributions welcome ). I thought it had an escape hatch to insert it yourself, but it does not. Let me know if this is an important feature for you in the short term, then I can prioritise its implementation.
I’m not sure why they’re using both Dates and DateTimes, but given the context, I’m assuming it’s the difference between a full-day appointment and something at a specific time/duration.
I’m not quite sure what it’s trying to do there, but I’m expecting it to be a bug in mashlib. It appears that it’s assuming some data to be there that there is not yet, but it’s hard to debug from that error message.
Hmm, rdf-namespaces is automatically generated from the vocabularies published at the given URLs. For each URL you mentioned, there appears to be a different reason it is not included:
Not use it, since it’s technically not part of that vocabulary.
Use the URL directly. The values from rdf-namespaces are just URLs, so you could just use 'https://www.w3.org/2005/01/wf/flow#partcipant' where you’d use wf.participant instead.
dc.created
Could it be that you’d want dct.created (so dct instead of dc) instead? Because DCMI: DCMI Metadata Terms doesn’t point to anything either.
rdf.nil
This is interesting. This property is defined at http://www.w3.org/1999/02/22-rdf-syntax-ns#nil, but it’s defined as being an rdf:List rather than an rdfs:Class or rdf:Property, for instance, which is why rdf-namespaces doesn’t include it - because it’s not technically a type, but a value (specifically, an -the- empty list). As a workaround, here too you can use the full URL ('http://www.w3.org/1999/02/22-rdf-syntax-ns#nil') instead of rdf.nil.
Which reminds me: the earlier code snipped I posted probably also needs: