Organize ontology and documentation files in release package into subdirectories by file type

[rjyounes]

The suggestions is for the release package to look like this:

ontologies/
    turtle/
        gistCore.ttl
        gistSubClassAssertions.ttl
        etc.
    json-ld/
        gistCore.jsonld
        gistSubClassAssertions.jsonld
        etc.
    rdf-xml/
        gistCore.rdf
        gistSubClassAssertions.rdf
        etc.

This reduces clutter in the ontologies directory, and makes it easier for someone to get what they want (generally someone wants only files of a particular serialization).

Do the same for HTML and Markdown files in the docs directory.

[coltonglasgow]

@rjyounes I agree with the proposed directory structure of the ontologies directory. The docs directory is a little more complex because of the models subdirectory. This is what the docs directory looks like from the current bundler:

I propose we use markdown as the primary documentation file type with an HTML directory for the generated HTML:

Alternatively, I could create the suggested structure for each directory. This will add some complexity to the bundle file and will add a lot of extra directories to the bundled gist package:

How should I handle the docs directory?

[Jamie-SA]

Why not just have the models directory under the HTML and the Markdown directories?

• docs
  • HTML
    • models
  • Markdown
    • models

[stevenchalem]

I like Colton's first suggestion, possibly modified to:

• docs
  • html
    • models
    • ReleaseNotes.html
  • models
  • ReleaseNotes.md

Also I suggest lowercasing HTML and (if we use it) Markdown. Otherwise these would be the only directory names not in lower case.

[rjyounes]

I agree with Steven about the letter casing. Leaning towards Jamie's suggestion for directory structure but could live with Colton's first suggestion. I agree that what I had originally proposed is clunky.

[coltonglasgow]

I have implemented the following based on feedback above: