Skip to content

Latest commit

 

History

History
142 lines (129 loc) · 6.06 KB

index.md

File metadata and controls

142 lines (129 loc) · 6.06 KB
Raw
container-id type work-package pilot funder credits layout title nav_order permalink ecosystem-release
polifonia-project
Project
WP1
WP2
WP3
WP4
WP5
WP6
WP7
WP8
TUNES
BELLS
INTERLINK
MUSICBO
TONALITIES
MEETUPS
CHILD
ORGANS
ACCESS
FACETS
name url grant-agreement
Horizon 2020 Framework Programme
This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement N. 101004746.
default
Home
0
/
v2.0

SPICE Ecosystem ({{ page.ecosystem-release }})

{: .fs-9 }

Data, software, and documentation of the output of the EU H2020 project [SPICE]({{ site.main-project-url }}.). {: .fs-6 .fw-300 }

The SPICE Ecosystem is a collection of components for developing intelligent applications leveraging musical cultural heritage, result of the Polifonia Project. The project aims at realising and deploying anecosystem of computational methods and tools supporting discovery, extraction, encoding, interlinking, classification, exploration of, and access to, musical heritage knowledge on the Web.

{% comment %} SPICE development methodology is two ways. It follows a bottom-up approach, ensuring that the development is participatory, agile, feature driven, and collaborative. However, this is paired with a top-down approach, where a Technical Board interacts with WP leaders to ensure the objectives of the project are fully met.

The components are both independent – they have some value on their own – and interlinked – they can be used together in order tosatisfy specific end-user needs. Independence is a well known principle of software engineering, which is conceived alongside the one of inter-operability - the ability of a software componentto operate with others. However, the possible connections between ecosystem components don’t necessarily derive from software-to-software relations but involve, for example, users being able to perform a complex task by using multiple tools, whose user interfaces are linked, or enable users to transfer data from one environment to another thanks to the mutual support of shared formats. The SPICE Project delivers its results as reusable assets, alongside an extensive metadata set and documentation. This is the Polifonia Ecosystem. {% endcomment %} {% assign types = site.documents | map: 'type' | join: ',' | split: ',' | uniq | sort %}

{% comment %}

Summary

<script> anychart.onDocumentReady(function() { // set the data /* var data = [ {x: "Application", value: 1}, {x: "CLITool", value: 2}, {x: "Corpus", value: 1}, {x: "Dataset", value: 4}, {x: "Documentation", value: 4}, {x: "KnowledgeGraph", value: 1}, {x: "Lexicon", value: 1}, {x: "Library", value: 1}, {x: "Ontology", value: 6}, {x: "Persona", value: 22}, {x: "Project", value: 3}, {x: "Repository", value: 4}, {x: "RequirementsCollection", value: 2}, {x: "Schema", value: 2}, {x: "Service", value: 1}, {x: "Software", value: 8}, {x: "SoftwareLibrary", value: 1}, {x: "Story", value: 35}, {x: "Tutorial", value: 1}, {x: "UserInterface", value: 2}, {x: "WebApplication", value: 3}, {x: "WebServer", value: 1} ]; */ var data = [ {x: "Activites", value: 22}, {x: "Data", value: 18}, {x: "Software", value: 10}, {x: "Application", value: 6}, {x: "Report", value: 64} ] // create the chart var chart = anychart.pie3d(); // set the chart title // chart.title("Polifonia Project Components by Type"); // add the data chart.data(data); // sort elements chart.sort("desc"); // set legend position chart.legend().position("right"); // set items layout chart.legend().itemsLayout("vertical"); // display the chart in the container chart.container('chart_container'); chart.draw(); }); </script> {% assign types_activity = "Container,Project,WorkingGroup,WorkPackage,Task,UseCase,Pilot" | split: "," %} {% assign ncomponents = site.documents | where_exp: 'item',"types_activity contains item.type" | size %} {% assign npages = site.pages | where_exp: 'item',"types_activity contains item.type" | size %} {% assign nactivities = npages | plus: ncomponents %} {% endcomment %}

The ecosystem includes {% assign types_data = "Data,Dataset,Schema,Repository,Registry,Ontology,Corpus,Lexicon,KnowledgeGraph" | split: "," %}{% assign ncomponents = site.documents | where_exp: 'item',"types_data contains item.type" | size %} {{ncomponents}} data, {% assign software_data = "Software,Workflow,API,UserInterface,SofwareLibrary,DockerImageContainer,Notebook,Script,Application,Website,WebApplication,WebService,SPARQLEndpoint,MobileApp,CLITool" | split: "," %} {% assign ncomponents = site.documents | where_exp: 'item',"software_data contains item.type" | size %} {{ncomponents}} tools, {% assign report_data = "Report,RequirementsCollection,Story,Persona,Mockup,Surbey,InPresenceGroup,Documentation,Tutorial,EvaluationReport" | split: "," %}{% assign ncomponents = site.documents | where_exp: 'item',"report_data contains item.type" | size %} and {{ncomponents}} reports.

Polifonia content is managed on [GitHub](http://github.com/{{ site.github }}).

{% comment %}

All types

{% for type in types %} {% assign ncomponents = site.documents | where: 'type', type | size %} {% if ncomponents > 0 %} {{ type }}: {{ ncomponents }} {% endif %} {% endfor %}

List of components

{% for type in types %} {% if type != "" %}

{{ type }} ({{ site.documents | where: 'type',type | size }})

{% assign components =  site.documents  | where: 'type',type %}
{% for component in components %}
  • [{{ component.name }}]({{ component.url | relative_url }}) {% endfor %} {% endif %} {% endfor %} style="width: 100%; height: 100%" {% endcomment %}