bioterms landing page

[nsheff]

Currently bioterms.org points to:

Test Page
This page is used to test the proper operation of the Apache HTTP server after it has been installed. If you can read this page, it means that the Apache HTTP server installed at this site is working properly.

We need to think of a landing page.

[nsheff]

Hey @nmagee would it be easy to throw up a basic "welcome" page on bioterms.org ? Right now it yields a 403 error

[nmagee]

Sure thing — I can add that today.

[nmagee]

@nsheff These are in place now -- a welcome page and a schemas page to actually get to things. This is (again) using some simple BootStrap templates, with placeholder design and verbiage. But at least it gives a starting structure and a way to drill down to the schemas Ognen has set up.

[nmagee]

@nsheff based on closing #3 do you need me to work on more bioterms.org content or do you have that from here? I'm moving on extending my Python in episb.org now but can come back to this as you need.

[nmagee]

I did notice one fix we might need @oddodaoddo -- do we need bioterms.org to serve up schemas with or without the jsonld suffix?

So these would be equivalent: http://bioterms.org/schemas/Annotation.jsonld http://bioterms.org/schemas/Annotation

I only notice because within the actual JSONLD they make mention of schemas without the suffix:

  "@graph": Array[19][
    {
      "@id": "http://bioterms.org/schemas/Segment",
      "@type": "rdfs:Class",
      "rdfs:comment": "Basic definition of a dna segment",
      "rdfs:label": "Segment",
      "rdfs:SubclassOf": Array[2][
        {
          "@id": "https://schema.org/Intangible"
        },
        {
          "@id": "https://schema.org/ListItem"
        }
      ]
    }

[oddodaoddo]

Let me think about this... I think we do not need the .jsonld extension but I will double check.

On Fri, Dec 7, 2018 at 12:20 PM Neal Magee notifications@github.com wrote:

I did notice one fix we might need @oddodaoddo https://github.com/oddodaoddo -- do we need bioterms.org to serve up schemas with or without the jsonld suffix?

So these would be equivalent: http://bioterms.org/schemas/Annotation.jsonld http://bioterms.org/schemas/Annotation

I only notice because within the actual JSONLD they make mention of schemas without the suffix:

"@graph": Array[19][ { "@id": "http://bioterms.org/schemas/Segment", "@type": "rdfs:Class", "rdfs:comment": "Basic definition of a dna segment", "rdfs:label": "Segment", "rdfs:SubclassOf": Array[2][ { "@id": "https://schema.org/Intangible" }, { "@id": "https://schema.org/ListItem" } ] }

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/databio/bioterms/issues/1#issuecomment-445303089, or mute the thread https://github.com/notifications/unsubscribe-auth/AHTn3H1xRrEXwyvxWJkBa9upCKKhocj7ks5u2qN6gaJpZM4YOg2R .

[nsheff]

@nsheff based on closing #3 do you need me to work on more bioterms.org content or do you have that from here? I'm moving on extending my Python in episb.org now but can come back to this as you need.

I can work on the landing page now. Thanks!

do we need bioterms.org to serve up schemas with or without the jsonld suffix?

This is related to #5

[nsheff]

Latest commit has a more approachable description on the landing page, so I'm closing this issue.