Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: When to make a new vocabulary...

From: Boris Kolpackov <boris@-------------.--->
To: "Fortuno, Adam" <Adam.Fortuno@---------.--->
Date: 8/10/2007 10:14:00 PM
Hi Adam,

Fortuno, Adam <Adam.Fortuno@M...> writes:

> Consumer lending is different enough from mortgage lending that I would
> prefer to develop a new vocabulary to handle it. However, other believe
> strongly we should modify the existing schema.

I would say create a new vocabulary. If the two have a substantial
sub-vocabulary in common, factor it out into a base vocabulary (e.g,
call it basic-lending) and reuse it in both consumer-lending and
mortgage-lending.

BTW, this problem is pretty similar to the OO problem of creating two
separate classes vs lumping two relatively unrelated functionalities
into one class. I believe the consensus in OO is to create two classes
with a common base if necessary.


HTH,
Boris

-- 
Boris Kolpackov
Code Synthesis Tools CC
http://www.codesynthesis.com
Open-Source, Cross-Platform C++ XML Data Binding

From cmsmcq@a... Tue Aug 14 18:19:18 2007
Received: from aji.w3.org ([1


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent