✅ Deploy Preview for s-forms-kbss ready!

Name	Link
🔨 Latest commit	fb8d67b
🔍 Latest deploy log	https://app.netlify.com/sites/s-forms-kbss/deploys/66154de1b1a38100097c353a
😎 Deploy Preview	https://deploy-preview-315--s-forms-kbss.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Good point that it is breaking change, although not for SPipes applications but SPipesComponents. Thus we need to do it little later after we publish new version of SForms. Then we publish next version that will contain this change.

Moreover, we need to discuss conventions.E.g. we have:
Vocabulary.XSD.MAX_EXCLUSIVE
but
Vocabulary.RDFS_LABEL
-- we could also have Vocabulary.DOC, Vocabulary.FORM etc.

Other issues:

• strange namespace "http://onto.fel.cvut.cz/ontologies/aviation/form-376/is-disabled"; -> should be removed
• deprecated namespace static HELP_DESCRIPTION = "http://purl.org/dc/elements/1.1/description"; -> Refactor to Vocabulary.DCTERMS with prefix "http://purl.org/dc/terms/", i.e. it will end up http://purl.org/dc/terms/description.

BTW, you can use https://prefix.cc/ to search for meaningful prefixes of URIs.

@LaChope I changed last comment to address "Other issues". Note that after changing HELP_DESCRIPTION we should change also forms (e.g. ava-model).

Moreover, we need to discuss conventions.E.g. we have: Vocabulary.XSD.MAX_EXCLUSIVE but Vocabulary.RDFS_LABEL -- we could also have Vocabulary.DOC, Vocabulary.FORM etc.

I am not sure I understand fully in the end. For instance, these should be refactored like so?

static HAS_OPTION => FORM.HAS_OPTION
static HAS_OPTIONS_QUERY => FORM.HAS_OPTION_QUERY
static HAS_ANSWER => DOC.HAS_ANSWER
...

yes