Introduction to Linked Code
LINCD.js provides various helper methods to link your code to Linked Data structures.
By linking code to data we know exactly what sort of data is required to use certain bits of code. That means that if we ensure the data has this format, the code will run as expected without any further configuration.
Imagine supplying a single data source to a component and trusting that all the nested sub properties and other bits of related data that the component requires will magically be found.
That's what becomes possible when we link our code to our data.
The benefits of linking code to data works both ways.
If you start with data you can find matching code. Or if you start with code you can easily create or find matching data:
1) Find matching components for specific data
Convert your data to Linked Data, choose the most fitting ontologies in the process.
After this you can find available components and functionality (in Shapes) that are available for your data without any extra coding or configutation.
2) Get the right data for chosen components
First, choose the components you want to use in your application. Now you know exactly what sort of data you need to provide. Which ontologies it needs to use, which classes, which properties.
This can be used by tools to help you convert your data. Alternatively you can obtain your data externally and easily validate it or convert it on the fly.
Once you have your data, it can be supplied to your chosen component as is, without any further changes or configuration.
Get started with Linked Code
Exciting stuff right?
That's why we encourage you to follow these guides to learn how you can use LINCD.js to create Linked Code.
LINCD links ontologies (data structures) to components with shapes.
All of these are bundled into LINCD packages.
Go ahead and read how you can create your own LINCD packages next!