There should be a way to specify Schema file that is part of the project

During active development, especially for a small or local or private project there is no justification to post schema to some hosted location, like Schema store.

yaml.schemas settings should allow specifying ${workspaceFolder} placeholder in file:///local-path or, ideally, just recognize relative path notation

For example: /schemas/my-schema.json should mean that schema file is located in file:///${workspaceFolder}/schemas/my-schema.json

The only way it works right now is if we specify absolute path of the schema file on local file system in Worspace settings file, but it doesn't work in generall, because different developers / dev boxes have different folder names/structure.

VSCode-yaml extension v0.0.16
VSCode: (windows portable install)
Version: 1.27.2
Commit: f46c4c469d6e6d8c46f268d1553c5dc4b475840f
Date: 2018-09-12T16:17:45.060Z
Electron: 2.0.7
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64

Start by locating the handling of the yaml.schemas setting and how schema file URLs are resolved relative to workspace settings. Verify the behavior with a workspace containing schemas/my-schema.json; done means ${workspaceFolder} or the requested relative path resolves consistently without machine-specific absolute paths.