GitPlanet

Cheap and reliable Node.js hosting starts at $3/month, and $1/month static HTML hosting

Created with love in Canada, visit hostnodejs.com today

Feel like to post an Ad? Learn Details
All Projects → ESIPFed → Sweet

ESIPFed / Sweet

Licence: other
Official repository for Semantic Web for Earth and Environmental Terminology (SWEET) Ontologies

Labels

makefileenvironmentenvironment-variablesearth

Projects that are alternatives of or similar to Sweet

ini
📝 Go INI config management. support multi file load, data override merge. parse ENV variable, parse variable reference. Dotenv file parse and loader. INI配置读取管理，支持多文件加载，数据覆盖合并, 解析ENV变量, 解析变量引用。DotEnv 解析加载
Stars: ✭ 72 (+4.35%)
Mutual labels:  environment, environment-variables
dart environment config
Environment specific config generator for Dart and Flutter applications during CI/CD builds
Stars: ✭ 87 (+26.09%)
Mutual labels:  environment, environment-variables
as-a
Runs a given command with additional environment settings for simple local development
Stars: ✭ 60 (-13.04%)
Mutual labels:  environment, environment-variables
Variable Injector
Continuous Integration Tool for Swift Projects
Stars: ✭ 63 (-8.7%)
Mutual labels:  environment, environment-variables
gatsby-plugin-dynamic-routes
Creating dynamic routes based on your environment and/or renaming existing routes
Stars: ✭ 14 (-79.71%)
Mutual labels:  environment, environment-variables
Environ Config
Python Application Configuration With Environment Variables
Stars: ✭ 210 (+204.35%)
Mutual labels:  environment, environment-variables
rune
tool to query for tokens and passwords for use as environment variables
Stars: ✭ 13 (-81.16%)
Mutual labels:  environment, environment-variables
Fig
A minimalist Go configuration library
Stars: ✭ 142 (+105.8%)
Mutual labels:  environment, environment-variables
ts-dotenv
Strongly-typed environment variables for Node.js
Stars: ✭ 18 (-73.91%)
Mutual labels:  environment, environment-variables
ngx-env
Easily inject environment variables into your Angular applications
Stars: ✭ 73 (+5.8%)
Mutual labels:  environment, environment-variables
Env Var
Verification, sanitization, and type coercion for environment variables in Node.js
Stars: ✭ 201 (+191.3%)
Mutual labels:  environment, environment-variables
angular-environment
AngularJS Environment Plugin
Stars: ✭ 78 (+13.04%)
Mutual labels:  environment, environment-variables
Emacs Direnv
direnv integration for emacs
Stars: ✭ 194 (+181.16%)
Mutual labels:  environment, environment-variables
dotenvy
Speed up your production sites by ditching .env for key/value variable pairs as Apache, Nginx, and shell equivalents
Stars: ✭ 31 (-55.07%)
Mutual labels:  environment, environment-variables
Envy
Envy automatically exposes environment variables for all of your Go flags
Stars: ✭ 150 (+117.39%)
Mutual labels:  environment, environment-variables
DBEnvironmentConfiguration
Easily switch between iOS development environments/ configurations
Stars: ✭ 18 (-73.91%)
Mutual labels:  environment, environment-variables
Env Providers
👷 Load Laravel service providers based on your application's environment.
Stars: ✭ 73 (+5.8%)
Mutual labels:  environment, environment-variables
Envinject Plugin
This plugin makes it possible to setup a custom environment for your jobs
Stars: ✭ 74 (+7.25%)
Mutual labels:  environment, environment-variables
acre
Lightweight configurable environment management in Python
Stars: ✭ 20 (-71.01%)
Mutual labels:  environment, environment-variables
envmnt
Environment variables utility functions.
Stars: ✭ 16 (-76.81%)
Mutual labels:  environment, environment-variables
View All Similar Projects ➔

SWEET Ontologies

Chat on Slack on channel #sweetontology

Introduction

Official repository for Semantic Web for Earth and Environmental Terminology (SWEET) Ontologies.

View in pyLODE View in WebVowl View in ESIP COR
View in GitHub View raw RDF Download RDF

What is SWEET?

SWEET is a highly modular ontology suite with ~6000 concepts in ~200 separate ontologies covering Earth system science. SWEET is a mid-level ontology and consists of nine top-level concepts that can be used as a foundation for domain-specific ontologies that extend these top-level SWEET components. SWEET’s own domain-specific ontologies, which extend the upper level ontologies, can provide users interested in further developing a particular domain with a solid set of concepts to get started. SWEET ontologies are written in W3C Turtle; the Terse RDF Triple Language.

SWEET as Linked Data

Details of how HTTP requests against http://sweetontology.net are processed can be found here.

SWEET IRI Patterns for Ontologies and their Terms

See the relevant wiki documentation.

Community

SWEET is governed by the ESIP Semantic Technologies Committee (STC) meaning that all proposed changes are evaluated by a number of subject matter experts. If you would like to learn more about SWEET, or are interested in joining the community, please join our community mailing list.

Recognition of SWEET Contributors

Ensure you are recognized for your contributions.

Development

Please see the CONTRIBUTING documentation.

Additionally, if you wish to discuss SWEET issues with the STC, please contact us via the WG email list.

Using local copies of ontology

The sweetall.ttl ontology imports all the other sweet components via URL. If you are offline, or working on updates that require using the local copies of the ontology files, copy the catalog-v001.xml file from the root directory of the repository into the src directory before opening sweetAll.ttl in Protege.

License/Copyright

SWEET is available under the CC0 1.0 Universal Public Domain Dedication.

CC0
To the extent possible under law, SWEET Ontology Developers have waived all copyright and related or neighboring rights to the Semantic Web for Earth and Environmental Terminology (SWEET) Ontology Suite.

A copy of the CC0-1.0 ships with this repository.

Prior to SWEET 3.5.0, SWEET was licensed under the Apache License v2. For more information on the change, see here.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].