Op 20-9-2013 17:01, Thomas Beale schreef: > it's simpler than you think - we made that property mandatory so that > programmers would never get a null exception. Must have been along time ago, nowerdays, programmers have no problem handling a null property.
I wonder what the idea behind stuffing the archetype_id in the archetype_node_id property is? Here you make it harder for programmers because the archetype_id has another syntax in archetype-paths then the archetype_node_id has, and anyway, lots of other functions, and a programmer has to check the string-layout to find out if it is an archetype_id or an archetype_node_id. It also blocks the possibility to store the "at"-code for the root, and check the ontology for its contents. Bert
