Download the PHP package openeuropa/rdf_skos without Composer

On this page you can find all versions of the php package openeuropa/rdf_skos. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package rdf_skos

RDF SKOS

This module provides a dedicated entity type for SKOS modeling. The module requires access to a triplestore database, such as Virtuoso 7.

Upgrade from 0.11.0 to 1.0.0-alpha1

On 1.0.0-alpha1, the rdf_entity module dependency has been removed and instead the sparql_entity_storage module has been introduced (see the rdf_entity module's Readme for more information).

As suggested by the rdf_entity module itself, the following steps can be taken in order to update rdf_skos in production:

The update process needs to be split in three deployments, which will likely result into separate site releases.

First deployment

  1. Before you update rdf_skos to 1.0.0-alpha1, require an empty version of the drupal/sparql_entity_storage module:

  2. Deploy to production.
  3. Enable the module (this can be part of the deployment procedure above, depending on your setup).

At this point your site's composer.json should look like this:

Second deployment

  1. Remove the empty drupal/sparql_entity_storage module requirement from your composer.json.
  2. Require drupal/rdf_entity with the new 1.0-alpha21 version and openeuropa/rdf_skos with the new 1.0.0-alpha1 version.
  3. Deploy to production.
  4. Uninstall the drupal/rdf_entity module (this can be part of the deployment procedure above, depending on your setup).

At this point your site's composer.json should look like this:

Third deployment

  1. Remove the drupal/rdf_entity dependency.
  2. Deploy to production.

At this point your site's composer.json should look like this:

After these steps your site should have the latest version drupal/rdf_skos module using drupal/sparql_entity_storage and the drupal/rdf_entity module should no longer be in your codebase.

Technical details and constraints

The module allows loading SKOS concept schemes and concepts as entities in Drupal. The entities will be loaded from the graph IRIs specified in the related configuration.

Since all the graphs are passed to the methods for loading entities, this enforces the limitation of having unique IRIs (IDs in Drupalese) for the SKOS entities present in all the graphs.

Development setup

Initial setup

You can build the test site by running the following steps.

This will symlink the module in the proper directory within the test site and perform token substitution in test configuration files such as behat.yml.dist.

Please note: project files and directories are symlinked within the test site by using the OpenEuropa Task Runner's Drupal project symlink command.

If you add a new file or directory in the root of the project, you need to re-run drupal:site-setup in order to make sure they are be correctly symlinked.

If you don't want to re-run a full site setup for that, you can simply run:

Your test site will be available at ./build.

Using Docker Compose

Alternatively you can build a test site using Docker and Docker-compose with the provided configuration.

Requirements:

You can make any alterations you need for your local Docker setup. However, the defaults should be enough to set the project up.

Run:

Then:

Your test site will be available at http://localhost:8080/build.

To run the grumphp test:

To run the phpunit test:

To run the behat test:

Working with content

The project ships with the following Task Runner commands to work with content in the RDF store, they require Docker Compose services to be up and running.

Purge all data:

Or, if you can run commands on your host machine:

Import default data:

Or, if you can run commands on your host machine:

Reset all data, i.e. run purge and import:

Or, if you can run commands on your host machine:

All versions of rdf_skos with dependencies

PHP Build Version
Package Version
Requires php Version >=8.1
drupal/core Version ^10
drupal/sparql_entity_storage Version ^2.0.0-alpha12
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package openeuropa/rdf_skos contains the following files

Loading the files please wait ....