ADIwg Schema Viewer misnamed?

[dwalt]

I ran into a confusing point in the process of writing documentation for the schema viewer. The GUI tool is actually more than the Viewer. It provides an interface for the Schema Viewer, the Validator and the Translator. It also provides a toggle between the Viewer Tree and the Viewer Information tab. I think this is confusing to call this interface the ADIwg Schema Viewer. There really is an all encompassing interface that is providing modal access to each of these tools, plus likely future tools. I think we should label this interface something different, like ADIwg Metadata Tool Navigator. Then you can sub-label according to the current tool mode. e.g.:

ADIwg Metadata Tool Navigator - ADIwg JSON Schema Viewer
ADIwg Metadata Tool Navigator - ADIwg JSON Validator

[jlblcc]

Yeah, I thought about this a while back. Didn't follow up on it...

We can call it something like mdTools or mdNavigator. We could call it mdApps, but then I'd puke. Just need to keep it short.

[stansmith907]

I kind of like mdTools right off, agree mdApps would make me puke too. The planned tab on links to resources (template, examples, etc.) could also have links to hosted resources like mdBook, the API, demo, and others. The would make it a great consolidated entry point.

[dwalt]

mdTools works for me

On Fri, Jan 16, 2015 at 3:22 PM, stansmith907 notifications@github.com
wrote:

I kind of like mdTools right off, agree mdApps would make me puke too. The
planned tab on links to resources (template, examples, etc.) could also
have links to hosted resources like mdBook, the API, demo, and others. The
would make it a great consolidated entry point.

—
Reply to this email directly or view it on GitHub
#4 (comment).