[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Different Roots in Jliff
All Sorry for the implementational nature of this email. Just looking at my code again. In looking at various ways to support different roots I came up with the notion of a generic Jliff<T> where T would signal the root. My recollection is that it worked nicely from a programming perspective. A consequence of this is that we would want a single property name in the wrapper to assign the root to as opposed to individual property names like fragment, units, groups, and subunits. in the fourth schema. My generic implementation
uses “content” as that property name (though I guess it could also be root). Are we wedded to having four properties, one for each root type? I haven’t considered my implementation as open source at the moment but perhaps if anyone was interested in looking at the code I could just give those people individual access to my code without commitment to open source. Phil
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]