Set up DNS for Table Schema Catalog website

[monikappv]

Get the website up and running.

Acceptance

• schemas.datahub.io / schemas.frictionlessdata.io is live
• the site looks the same way in production as it does in development mode

Tasks

• contact Adria
• ...

[monikappv]

@amercader
hey I heard I should reach out to you for stuff like that. could you take this on?
We want to go live and the initial idea was to use schemas.frictionlessdata.io, but as far as I understood from @rufuspollock there are some issues there so we decided to go for schemas.datahub.io for now.
@rufuspollock please confirm if that is correct.

[lwinfree]

hey @rufuspollock I think this URL should be schemas.frictionlessdata.io. What are the issues there? Could you please list here so myself & @amercader can help resolve issues to make it happen?

[rufuspollock]

I think the issue atm is that schemas.frictionlessdata.io is reserved and needed for some parts of the tooling to run. Let's check this with @roll before we do anything.

[roll]

Hi, the main libraries (Python/JS) don't use this endpoint in runtime so for them it's fine to remove it. On the other hand, there is no guarantee that some other software doesn't use it (e.g. OpenSpending).

Actually, I've been proposing for years to create a terminology distinction between:

• metadata profiles (JSON Schema) -> profile
• table schemas (Table Schema) -> schema

De-facto this terminology is used across all the core software because if some libraries have a schemas directory it's a terrible confusion point if you name both JSON Schemas and Table Schemas as schema (so JSON Schemas go to a profiles directory).

Maybe it's a long shot but I would propose:

• moving schemas.frictionlessdata.io -> profiles.frictionlessdata.io/api/v1/ (or something like this)
• hosting Schemas Catalogue on schemas.frictionlessdata.io
• adding redirects for all currently existent profiles from the schema site to the profiles site e.g. schemas.frictionlessdata.io/data-package.json -> profiles.frictionlessdata.io/api/v1/data-package.json
• in the future creating the Profiles Catalogue UI on profiles.frictionlessdata.io

PS.
Just to clarify, there is core difference between a profile and a schema in our case. The profile is a metadata of metadata while the schema is a metadata of data.

[lwinfree]

thanks @roll I like that idea. For the record, I have personally been confused by the profiles vs schema terminology in some places, so I think your proposal would be really helpful for users.