Handling Trademarks, Credits, Endorsements, Certificates, and End User Support

Some Suggestions

Note that the following are registered trademarks of NLM or its NIH parent organization. If you create your own independently-distributed version of this project, please change these names and logos, or reach a formal agreement with NLM to use them:

• NLM logo
• TriagePic name
• People Locator name and logo

Your version should clearly indicate that it is NOT supported or endorsed by the US government (see the license), unless a separate formal agreement to provide such support is established. However, a "...based on..." formulation may be graceful. Also, use of small-size NLM names and logos by reference in a "Powered by..." or other secondary reference is generally permitted. Within the app, and in supporting material, it is wise to spell how you would like your end users to get support.

Additional Considerations for Developers

This version of TriagePic is distributed through the Microsoft Store. At the point you intend to distribute your version (outside running it in Visual Studio), you could consider doing likewise, or use a Microsoft-defined (and more expensive) Enterprise distribution method.

In the manifest, you will need to change the name of the app and the publisher. If submitting to the Store, when creating an app package, you also MUST provide your own .pfx certificates. (See the "Credentials" section of "Code Methodology and Dependencies" for more about this.) Recall that Visual Studio allows generation of 1-year-duration certificates; or your organization may have its own.

Generally, your version of TriagePic will point to your organization's version of TriageTrak. This linkage will be baked in at TriagePic build-time, as configured by how you have set the Service Reference. (Extensive efforts to make this a run-time setting have come of naught.)