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

Phil Ritchie

Chief Technology Officer | Vistatec

Vistatec House, 700 South Circular Road,
Kilmainham, Dublin 8, Ireland.

Tel: +353 1 416 8000 | Direct: +353 1 416 8024

Email: 

www.vistatec.com | ISO 9001 | ISO 13485 | ISO 17100 | ISO 27001

Think Global

Vistatec Ltd. Registered in Ireland 268483. Registered Office, Vistatec House, 700, South Circular Road, Kilmainham. Dublin 8. Ireland.
 The information contained in this message, including any accompanying documents, is confidential and is intended only for the addressee(s). 
â??The unauthorized use, disclosure, copying, or alteration of this message is strictly forbidden. 
If you have received this message in error please notify the sender immediately.