{"id":13558511,"url":"https://github.com/TriplyDB/YALC","last_synced_at":"2025-04-03T13:31:31.567Z","repository":{"id":43048960,"uuid":"248795071","full_name":"TriplyDB/YALC","owner":"TriplyDB","description":"🕸 YALC: Yet Another LOD Cloud (registry of Linked Open Datasets).","archived":false,"fork":false,"pushed_at":"2023-08-21T09:32:40.000Z","size":8391,"stargazers_count":14,"open_issues_count":0,"forks_count":4,"subscribers_count":9,"default_branch":"master","last_synced_at":"2024-11-04T09:37:24.386Z","etag":null,"topics":["json-ld","linked-data","linked-open-data","lod-cloud","open-data","rdf","semantic-web"],"latest_commit_sha":null,"homepage":"https://triplydb.com","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/TriplyDB.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2020-03-20T15:54:23.000Z","updated_at":"2024-07-29T12:24:41.000Z","dependencies_parsed_at":"2024-11-04T09:31:07.302Z","dependency_job_id":null,"html_url":"https://github.com/TriplyDB/YALC","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TriplyDB%2FYALC","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TriplyDB%2FYALC/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TriplyDB%2FYALC/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TriplyDB%2FYALC/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/TriplyDB","download_url":"https://codeload.github.com/TriplyDB/YALC/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":247009616,"owners_count":20868578,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["json-ld","linked-data","linked-open-data","lod-cloud","open-data","rdf","semantic-web"],"created_at":"2024-08-01T12:04:59.561Z","updated_at":"2025-04-03T13:31:28.754Z","avatar_url":"https://github.com/TriplyDB.png","language":"Shell","funding_links":[],"categories":["Shell","open-data"],"sub_categories":[],"readme":"\u003cimg src=\"img/triply.png\" align=\"right\" height=\"150\"\u003e\n\n[![](https://img.shields.io/badge/datasets-338-brightgreen)](datasets)\n[![](https://img.shields.io/badge/organizations-102-brightgreen)](organizations)\n[![](https://img.shields.io/badge/tooLittleInfo-25-yellow)](datasets/too-little-info)\n[![](https://img.shields.io/badge/todo-14-red)](datasets/todo)\n[![](https://img.shields.io/badge/errors-56-red)](datasets/errors)\n\n# YALC: Yet Another LOD Cloud\n\nThis repository contains configuration files for Linked Open Datasets\nthat are published on the web.  These datasets can be freely used at\n\u003chttps://triplydb.com\u003e.\n\n## Get started\n\nGo to https://triplydb.com and use the search bar to search for\ndatasets.\n\n## Contribute\n\nIf your favorite Linked Dataset is not yet available at\n\u003chttps://triplydb.com\u003e, you can add its configuration in a [pull\nrequest](https://github.com/TriplyDB/YALC/pulls) or you can open a\n‘Dataset request’ [issue](https://github.com/TriplyDB/YALC/issues).\n\n## Repository structure\n\nThis repository contains the following directories:\n\n\u003cdl\u003e\n  \u003cdt\u003e\u003ca href=\"datasets\"\u003e\u003ccode\u003e/datasets\u003c/code\u003e\u003c/a\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    Contains one configuration file for each dataset.\n    \u003cdl\u003e\n      \u003cdt\u003e\u003ca href=\"datasets/errors\"\u003e\u003ccode\u003e/datasets/errors\u003c/code\u003e\u003c/a\u003e\u003c/dt\u003e\n      \u003cdd\u003eContains one configuration file for each dataset that cannot yet be uploaded because it contains errors.\u003c/dd\u003e\n      \u003cdt\u003e\u003ca href=\"datasets/todo\"\u003e\u003ccode\u003e/datasets/todo\u003c/code\u003e\u003c/a\u003e\u003c/dt\u003e\n      \u003cdd\u003eContains one configuration file for each dataset that cannot yet be uploaded because some functionality is still missing.\u003c/dd\u003e\n      \u003cdt\u003e\u003ca href=\"datasets/too-little-info\"\u003e\u003ccode\u003e/datasets/too-little-info\u003c/code\u003e\u003c/a\u003e\u003c/dt\u003e\n      \u003cdd\u003eContains partial configuration files for datasets for which too little information is available at the moment.\u003c/dd\u003e\n    \u003c/dl\u003e\n  \u003c/dd\u003e\n  \u003cdt\u003e\u003ca href=\"img\"\u003e\u003ccode\u003e/img\u003c/code\u003e\u003c/a\u003e\u003c/dt\u003e\n  \u003cdd\u003eContains images that are used in dataset and organization configurations.\u003c/dd\u003e\n  \u003cdt\u003e\u003ca href=\"organizations\"\u003e\u003ccode\u003e/organizations\u003c/code\u003e\u003c/a\u003e\u003c/dt\u003e\n  \u003cdd\u003eContains one configuration file for each organization.\u003c/dd\u003e\n  \u003cdt\u003e\u003ca href=\"rdf\"\u003e\u003ccode\u003e/rdf\u003c/code\u003e\u003c/a\u003e\u003c/dt\u003e\n  \u003cdd\u003eContains the RDF definitions that are used by the configuration files in this repository, and includes small RDF datasets that are part of the LOD Cloud but for which we could not find an online publication elsewhere.\u003c/dd\u003e\n\u003c/dl\u003e\n\n## Configuration format\n\nThe configuration files in YALC all follow a JSON configuration\nformat.  The following subsections document the format for dataset\nconfiguration files and the format for organization configuration\nfiles.\n\n### Dataset configuration format\n\nThe dataset configuration format is used for the files in the\n[`/datasets`](datasets) subdirectory.  Each file contains a JSON\nobject with the following keys:\n\n\u003cdl\u003e\n  \u003cdt\u003e\u003ccode\u003e\"about\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eZero or more topics that characterize what the dataset is about.\u003c/p\u003e\n    \u003cp\u003eTopic values must also appear in the \u003ca href=\"rdf/topics.jsonld\"\u003etopic hierarchy\u003c/a\u003e.  Topic values are specified with their IRI local name.  For example, \u003ccode\u003e\"eGov\"\u003c/code\u003e is used to denote the topic with IRI \u003ccode\u003ehttps://triplydb.com/Triply/yalc/id/topic/eGov\u003c/code\u003e.\u003c/p\u003e\n    \u003cp\u003eFor vocabularies, this key must include the value \u003ccode\u003e\"vocabulary\"\u003c/code\u003e.\u003c/p\u003e\n    \u003cp\u003eThis key is optional, in which case the dataset has zero topics.\u003c/dd\u003e\n\n  \u003cdt\u003e\u003ccode\u003e\"asset\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eLinks to binary files that are part of the dataset.\u003cp\u003e\n    \u003cp\u003eOne example is documentation files (DOCX, PDF, ODT) that either occur in the dataset or that describe it.  Another example is media files (images, sounds, videos) that occur in the dataset.\u003c/p\u003e\n    \u003cp\u003eThis key is optional.\u003c/p\u003e\n  \u003c/dd\u003e\n\n  \u003cdt\u003e\u003ccode\u003e\"description\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eThe description of the dataset.\u003c/p\u003e\n    \u003cp\u003eThis must be at least 50 characters and at most 1,000 characters long.\u003c/p\u003e\n    \u003cp\u003eThis key is required.\u003c/p\u003e\n  \u003c/dd\u003e\n\n  \u003cdt\u003e\u003ccode\u003e\"diagram\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eAn image showing a diagrammatic overview of the dataset.  This value must be the local name for a file in the \u003ca href=\"img\"\u003e\u003ccode\u003e/img\u003c/code\u003e\u003c/a\u003e subdirectory.\u003c/p\u003e\n    \u003cp\u003eThis key is optional.\u003c/p\u003e\n  \u003c/dd\u003e\n\n  \u003cdt\u003e\u003ccode\u003e\"graph\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eSpecifies the named graph that will be used to store the content from the default graph in.\u003c/p\u003e\n    \u003cp\u003eThis key is optional.\u003c/p\u003e\n    \u003cp\u003eIf this key is not specified and exactly one prefix is specified, then the prefix IRI is used as the default graph name.\u003c/p\u003e\n  \u003c/dd\u003e\n\n  \u003cdt\u003e\u003ccode\u003e\"homepage\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eThe URL of the web page that is the authoritative location on the Internet for human-readable information about the dataset.\u003c/p\u003e\n    \u003cp\u003eSometimes a dataset does not have its own web page.  In such cases it is possible to specify a web page that describes or mentions the dataset.\u003c/p\u003e\n    \u003cp\u003eThis key is optional, in which case the dataset will have no homepage.\u003c/p\u003e\n  \u003c/dd\u003e\n\n  \u003cdt id=\"dataset-id\"\u003e\u003ccode\u003e\"id\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eIdentifies the dataset and (optionally) its organization and version.  The format for this value is \u003ccode\u003e\"ORGANIZATION/DATASET@VERSION\"\u003c/code\u003e.\u003c/p\u003e\n    \u003cp\u003eThe values for \u003ccode\u003eORGANIZATION\u003c/code\u003e and \u003ccode\u003eDATASET\u003c/code\u003e must be at least 2 and at most 40 characters long.  They must consist of digits (\u003ccode\u003e[0-9]\u003c/code\u003e), letters (\u003ccode\u003e[A-Za-z]\u003c/code\u003e), and hyphens (\u003ccode\u003e-\u003c/code\u003e).\u003c/p\u003e\n    \u003cp\u003eThe value for \u003ccode\u003eORGANIZATION\u003c/code\u003e must correspond with a file named \u003ccode\u003eORGANIZATION.json\u003c/code\u003e in the \u003ca href=\"organizations\"\u003e\u003ccode\u003e/organizations\u003c/code\u003e\u003c/a\u003e subdirectory.  See the \u003ca href=\"#organization-configuration-format\"\u003eorganization configuration\n     format section\u003c/a\u003e for more information.\u003c/p\u003e\n    \u003cp\u003eThe value of \u003ccode\u003eVERSION\u003c/code\u003e must follow one of the following formats:\u003c/p\u003e\n    \u003ctable\u003e\n      \u003cthead\u003e\n        \u003ctr\u003e\u003cth\u003eVERSION format\u003c/th\u003e\u003cth\u003eVERSION_OBJECT format\u003c/th\u003e\u003c/tr\u003e\n      \u003c/thead\u003e\n      \u003ctbody\u003e\n        \u003ctr\u003e\u003ctd\u003e\u003ccode\u003eMAJOR[.MINOR[.PATCH]]\u003c/code\u003e\u003c/td\u003e\u003ctd\u003e\u003ccode\u003e{\"@type\": \"SemanticVersion\", \"major\": \"MAJOR\", \"minor\": \"MINOR\", \"patch\": \"PATCH\"}\u003c/code\u003e\u003c/td\u003e\u003c/tr\u003e\n        \u003ctr\u003e\u003ctd\u003e\u003ccode\u003eYYYY\u003c/code\u003e\u003c/td\u003e\u003ctd\u003e\u003ccode\u003e{\"@type\": \"TemporalVersion\", \"year\": \"YYYY\"}\u003c/code\u003e\u003c/td\u003e\u003c/tr\u003e\n        \u003ctr\u003e\u003ctd\u003e\u003ccode\u003eYYYY-MM\u003c/code\u003e\u003c/td\u003e\u003ctd\u003e\u003ccode\u003e{\"@type\": \"TemporalVersion\", \"yearMonth\": \"YYYY-MM\"}\u003c/code\u003e\u003c/td\u003e\u003c/tr\u003e\n        \u003ctr\u003e\u003ctd\u003e\u003ccode\u003eYYYY-MM-DD\u003c/code\u003e\u003c/td\u003e\u003ctd\u003e\u003ccode\u003e{\"@type\": \"TemporalVersion\", \"date\": \"YYYY-MM-DD\"}\u003c/code\u003e\u003c/td\u003e\u003c/tr\u003e\n      \u003c/tbody\u003e\n    \u003c/table\u003e\n    \u003cp\u003eIf the organization that issues the dataset is not known, the \u003ccode\u003eORGANIZATION/\u003c/code\u003e prefix can be omitted.  If omitted, the ‘none’ organization will be used.\u003c/p\u003e\n    \u003cp\u003eIf the version of the dataset is not known, the \u003ccode\u003e@VERSION\u003c/code\u003e suffix can be omitted.  If omitted, \u003ccode\u003e\"1.0.0\"\u003c/code\u003e is used as the dataset version.\u003c/p\u003e\n    \u003cp\u003eThe \u003ccode\u003eDATASET\u003c/code\u003e part of this value is required.\u003c/p\u003e\n  \u003c/dd\u003e\n\n  \u003cdt\u003e\u003ccode\u003e\"image\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eThe logo or image for this dataset.  This value must be the local name for a file in the \u003ca href=\"img\"\u003e\u003ccode\u003e/img\u003c/code\u003e\u003c/a\u003e subdirectory.\u003c/p\u003e\n    \u003cp\u003eThis key is optional.  If it is omitted, the image of the dataset's organization (if any) is used.\u003c/p\u003e\n  \u003c/dd\u003e\n\n  \u003cdt\u003e\u003ccode\u003e\"license\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eThe license of this dataset.  The value must be one of the following:\u003c/p\u003e\n    \u003cul\u003e\n      \u003cli\u003e\u003ccode\u003ehttps://creativecommons.org/licenses/by-nc/4.0/\u003c/code\u003e\u003c/li\u003e\n      \u003cli\u003e\u003ccode\u003ehttps://creativecommons.org/licenses/by-sa/3.0/\u003c/code\u003e\u003c/li\u003e\n      \u003cli\u003e\u003ccode\u003ehttps://creativecommons.org/licenses/by/1.0/\u003c/code\u003e\u003c/li\u003e\n      \u003cli\u003e\u003ccode\u003ehttps://creativecommons.org/licenses/by/2.0/\u003c/code\u003e\u003c/li\u003e\n      \u003cli\u003e\u003ccode\u003ehttps://creativecommons.org/licenses/by/2.5/\u003c/code\u003e\u003c/li\u003e\n      \u003cli\u003e\u003ccode\u003ehttps://creativecommons.org/licenses/by/3.0/\u003c/code\u003e\u003c/li\u003e\n      \u003cli\u003e\u003ccode\u003ehttps://creativecommons.org/licenses/by/4.0/\u003c/code\u003e\u003c/li\u003e\n      \u003cli\u003e\u003ccode\u003ehttps://creativecommons.org/publicdomain/zero/1.0/\u003c/code\u003e\u003c/li\u003e\n      \u003cli\u003e\u003ccode\u003ehttps://opendatacommons.org/licenses/by/1-0/\u003c/code\u003e\u003c/li\u003e\n      \u003cli\u003e\u003ccode\u003ehttps://opendatacommons.org/licenses/odbl/1.0/\u003c/code\u003e\u003c/li\u003e\n      \u003cli\u003e\u003ccode\u003ehttps://opendatacommons.org/licenses/pddl/1-0/\u003c/code\u003e\u003c/li\u003e\n      \u003cli\u003e\u003ccode\u003ehttps://opensource.org/licenses/BSD-3-Clause\u003c/code\u003e\u003c/li\u003e\n    \u003c/ul\u003e\n    \u003cp\u003eThis key is optional.  Since datasets in YALC must have a license, the value \u003ccode\u003ehttps://creativecommons.org/licenses/by/4.0/\u003c/code\u003e is used in case this key is omitted.\n  \u003c/dd\u003e\n\n  \u003cdt\u003e\u003ccode\u003e\"name\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eThe display name of the dataset.\u003c/p\u003e\n    \u003cp\u003eThis key is optional.\u003c/p\u003e\n  \u003c/dd\u003e\n\n  \u003cdt\u003e\u003ccode\u003e\"namespace\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eZero or more IRIs that denote namespaces for this dataset.\u003c/p\u003e\n    \u003cp\u003eIRIs within these specified namespaces will have this dataset as their authority.  Ideally, every IRI has an authoritative dataset to which it belongs.  An IRI can have at most one authoritative dataset to which it belongs.\u003c/p\u003e\n    \u003cp\u003eThis key is optional.  If it is omitted and the \u003ccode\u003e\"prefix\"\u003c/code\u003e key is present, then the IRIs that appear in the value of the \u003ccode\u003e\"prefix\"\u003c/code\u003e key are used as the namespaces.\u003c/p\u003e\n  \u003c/dd\u003e\n\n  \u003cdt\u003e\u003ccode\u003e\"prefix\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eA JSON object containing RDF prefix declarations.  The keys of this JSON object are aliases that can be used to denote their corresponding IRI values.\u003c/p\u003e\n    \u003cp\u003eThis key is optional.\n  \u003c/dd\u003e\n\n  \u003cdt\u003e\u003ccode\u003e\"successor\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eAllows an outdated version of a dataset to point to its successor version.\u003c/p\u003e\n    \u003cp\u003eThe value notation is identical to the notation that is used for the \u003ca href=\"#dataset-id\"\u003e\u003ccode\u003e\"id\"\u003c/code\u003e\u003c/a\u003e key.\u003c/p\u003e\n  \u003c/dd\u003e\n\n  \u003cdt\u003e\u003ccode\u003e\"url\"\u003c/code\u003e\u003cdt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eZero or more URLs from which an RDF serialization of the dataset can be downloaded.\u003c/p\u003e\n    \u003cp\u003eThis key may be omitted if one or more namespaces are specified (see the documentation of the \u003ccode\u003e\"namespace\"\u003c/code\u003e key for more details).\u003c/p\u003e\n  \u003c/dd\u003e\n\u003c/dl\u003e\n\nThe following example shows the full dataset configuration for file\n`datasets/owl@2.0.json`.  Notice the following details:\n  - The value for key `\"id\"` is `\"w3c/owl@2.0\"`, whose prefix corresponds to the organization configuration file [`organizations/w3c.json`](organizations/w3c.json).\n  - The value for key `\"image\"` is\n`\"owl.png\"`, which corresponds to file [`img/owl.png`](img/owl.png).\n  - While the `\"namespace\"` key is not specified, its value is implicitly set to `\"http://www.w3.org/2002/07/owl#\"`, which is specified in the `\"prefix\"` key.\n  - While the `\"url\"` key is not specified, its value is implicitly set to `\"http://www.w3.org/2002/07/owl#\"`, because this is the (implicit) value of the `\"namespace\"` key.\n\n```json\n{\n  \"about\": \"vocabulary\",\n  \"description\": \"This ontology partially describes the built-in classes and properties that together form the basis of the RDF/XML syntax of OWL 2.  The content of this ontology is based on Tables 6.1 and 6.2 in Section 6.4 of the OWL 2 RDF-Based Semantics specification, available at \u003chttp://www.w3.org/TR/owl2-rdf-based-semantics/\u003e.\\n\\nPlease note that those tables do not include the different annotations (labels, comments and `rdfs:isDefinedBy` links) used in this file.  Also note that the descriptions provided in this ontology do not provide a complete and correct formal description of either the syntax or the semantics of the introduced terms (please see the OWL 2 recommendations for the complete and normative specifications).\\n\\nFurthermore, the information provided by this ontology may be misleading if not used with care. This ontology SHOULD NOT be imported into OWL ontologies. Importing this file into an OWL 2 DL ontology will cause it to become an OWL 2 Full ontology and may have other, unexpected, consequences.\",\n  \"homepage\": \"https://www.w3.org/TR/owl2-overview\",\n  \"id\": \"w3c/owl@2.0\",\n  \"image\": \"owl.png\",\n  \"name\": \"Web Ontology Language (OWL)\",\n  \"prefix\": {\n    \"owl\": \"http://www.w3.org/2002/07/owl#\"\n  }\n}\n```\n\n### Organization configuration format\n\nThe organization configuration format is used for files in the\n[`/organizations`](organizations) subdirectory.  Each file contains a JSON object with the following keys:\n\n\u003cdl\u003e\n  \u003cdt\u003e\u003ccode\u003e\"description\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eThe description of the dataset.\u003c/p\u003e\n    \u003cp\u003eThis must be at least 50 characters and at most 1,000 characters long.\u003c/p\u003e\n    \u003cp\u003eThis key is required.\u003c/p\u003e\n  \u003c/dd\u003e\n\n  \u003cdt\u003e\u003ccode\u003e\"homepage\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eThe URL of the main web page for human-readable information about the organization.\u003c/p\u003e\n    \u003cp\u003eThis key is optional, in which case the organization will have no homepage.\u003c/p\u003e\n  \u003c/dd\u003e\n\n  \u003cdt\u003e\u003ccode\u003e\"id\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eIdentifies the organization.\u003c/p\u003e\n    \u003cp\u003eThe value must be at least 2 and at most 40 characters long.  It must consist of digits (\u003ccode\u003e[0-9]\u003c/code\u003e), letters (\u003ccode\u003e[A-Za-z]\u003c/code\u003e), and hyphens (\u003ccode\u003e-\u003c/code\u003e).\u003c/p\u003e\n  \u003c/dd\u003e\n\n  \u003cdt\u003e\u003ccode\u003e\"image\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eThe logo or image for the organization.  This value must be the local name for a file in the \u003ca href=\"img\"\u003e\u003ccode\u003e/img\u003c/code\u003e\u003c/a\u003e subdirectory.\u003c/p\u003e\n    \u003cp\u003eThis key is optional.  If it is omitted, the image \u003ca href=\"/img/rdf.png\"\u003e\u003ccode\u003eimg/rdf.png\u003c/code\u003e\u003c/a\u003e is used.\u003c/p\u003e\n  \u003c/dd\u003e\n\n  \u003cdt\u003e\u003ccode\u003e\"name\"\u003c/code\u003e\u003c/dt\u003e\n  \u003cdd\u003e\n    \u003cp\u003eThe display name of the organization.\u003c/p\u003e\n    \u003cp\u003eThis key is optional.\u003c/p\u003e\n  \u003c/dd\u003e\n\u003c/dl\u003e\n\nThe following example shows the full organization configuration file\n[`organizations/w3c.json`](organizations/w3c.json):\n\n```json\n{\n  \"description\": \"The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.  Led by Web inventor and Director Tim Berners-Lee and CEO Jeffrey Jaffe, W3C's mission is to lead the Web to its full potential.  Contact W3C for more information.\",\n  \"homepage\": \"https://www.w3.org\",\n  \"id\": \"w3c\",\n  \"image\": \"w3c.png\",\n  \"name\": \"World Wide Web Consortium (W3C)\"\n}\n```\n\n### Semantic definitions\n\nThe configuration files in this repository can themselves be processed as Linked Data.  This is achieved by the following definition files:\n\n\u003cdl\u003e\n  \u003cdt\u003e\u003ca href=\"rdf/yalc.jsonld\"\u003e\u003ccode\u003e/rdf/yalc.jsonld\u003c/code\u003e\u003c/a\u003e\u003c/dt\u003e\n  \u003cdd\u003eConfiguration files can be processed as RDF by including the context stored in this file.\u003c/dd\u003e\n  \u003cdt\u003e\u003ca href=\"rdf/yalc.trig\"\u003e\u003ccode\u003e/rdf/yalc.trig\u003c/code\u003e\u003c/a\u003e\u003c/dt\u003e\n  \u003cdd\u003eDefinitions for the classes and properties that are used in the configuration files.\u003c/dd\u003e\n  \u003cdt\u003e\u003ca href=\"rdf/topics.jsonld\"\u003e\u003ccode\u003e/rdf/topics.jsonld\u003c/code\u003e\u003c/a\u003e\u003c/dt\u003e\n  \u003cdd\u003eTopic hierarchy that is used to tag datasets.\u003c/dd\u003e\n\u003c/dl\u003e\n\nThe Linked Data version of the configuration files is itself published [over here](https://triplydb.com/Triply/YALC).\n\n## Pull request details\n\nPull requests can be created to add new datasets, or to improve existing datasets.\n\n### Pull request for a new dataset\n\nIn order to add a new Linked Open Data to this repository, create a [pull request](https://github.com/TriplyDB/YALC/pulls) that includes at least the following:\n\n  - A dataset file `datasets/DATASET.json` whose contents adhere to the [dataset configuration format](#dataset-configuration-format).\n\nIf the organization that is specified in the dataset file does not yet have an organization file, it must be included as well:\n\n  - An organization file `organizations/ORGANIZATION.json` whose contents adhere to the [organization configuration format](#organization-configuration-format).\n\nIf the dataset and/or organization file specifies an image that does not yet belong to the `/img` subdirectory, then it must be added as well:\n\n  - A dataset image file and/or an organization image file in the `/img` directory.  The following image formats can be used: JPEG, PNG, SVG.  SVG images are preferred, since they are smaller in size and do not suffer from resolution issues.\n\n### Pull request for an existing dataset\n\nFeel free to improve the configurations for existing datasets.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2FTriplyDB%2FYALC","html_url":"https://awesome.ecosyste.ms/projects/github.com%2FTriplyDB%2FYALC","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2FTriplyDB%2FYALC/lists"}