You may adopt the standard — in whole or in part — into your own systems. You can feel free to extend (or scale back) the LMSS, tailored to your organization’s needs. But note that achieving the standard’s full benefit will involve incorporating the standard’s core framework. That will ensure interoperability between (1) your organization’s own systems and (2) external SALI-compliant organizations (e.g., clients, firms, vendors).
Creating custom codes? For many reasons, you should decline the urge to create home-grown, custom-built codes:
Embedding the LMSS. Some organizations (e.g., software vendors), offer value by including the LMSS in their off-the-shelf products. SALI can assist with this process: embedding the standard in your products and services in a form that most suits the needs of your clients and customers.
Mapping the LMSS. If replacing a legacy taxonomy with the LMSS is impractical, then a common and easier method is mapping your legacy codes to the LMSS. The standard was designed to accommodate many-to-one pairings.
In sum, SALI welcomes all forms of your implementations of the LMSS standard. And if you extend/enhance the LMSS, please let us know so that we can explore integration of your improvements into the LMSS standard. So your enhancements will make your organization’s data even more interoperable with other SALI-compliant organizations.
The SALI License. Lastly, SALI’s mission is to create standards that facilitate communication, not fragment it. So any SALI-licensed materials cannot be used to create competing standards. But any of our stakeholders (e.g., firms and legal service providers, vendors, clients, academics) can freely incorporate SALI into their systems. The public can access and use an XML implementation of our latest LSSS standard in our forthcoming GitHub repository, available under the MIT License. SALI's standard specification and associated documentation are licensed under the CC BY ND license.