<http://schema.org/articleBody>
"This logic is sound but seems limited. You're making the assumption that new program PrgZ6 can handle all the new functionality and then call PrgZ, but this won't always be the case. The new functionality maybe so entwined in PrgZ's logic that it can't be clinically separated like that. In that case, I suppose it would be better just to make PrgZ6 a clone of PrgZ with the new functionality added (and maybe move common functionality to a service program). Trevor Briggs Analyst/Programmer Lincare, Inc. (727) ..."^^<http://www.w3.org/2001/XMLSchema#string>
<http://archive.midrange.com/midrange-l/201401/msg00670.html>