=?utf-8?Q?Re=3A_=5Bxml-dev=5D_Create_fake_stuff_=28that=E2=80=99?==?utf-

[dal <dalapeyre@mulberrytech.com>]

JATS (journal article tag suite) tried for the 80/20
rule too. 80% of what real publishers were actually
doing, then modify as users request more or different
functionality.

Whether a Tag Set is a model or just a useful vocabulary,
80/20 makes for a usable and useful one.

—Debbie

 
> On Jan 22, 2017, at 3:27 AM, Stephen D Green <stephengreenubl@gmail.com> wrote:
> 
> The clever strategy is to invoke the 80:20 rule and aim to cover 80% of weather message requirements. When a requirement doesn't fit your schema you say it is part of the 20%. (Worked nicely with invoices and UBL.) Maybe 80:20 is a fake arbitrary split too but it works. Every model is an approximation.
> 
> 
> -- 
> ----
> Stephen D Green
> 


================================================================
Deborah A Lapeyre              mailto:dalapeyre@mulberrytech.com
Mulberry Technologies, Inc.      http://www.mulberrytech.com
17 West Jefferson Street         Phone: 301-315-9631 (USA)
Suite 207                        Fax:   301-315-8385
Rockville, MD 20850
----------------------------------------------------------------
Mulberry Technologies: Consultancy for XML, XSLT, and Schematron
================================================================