How-to mark up your own resource with Bioschemas
In this how-to, we will guide you through the necessary steps in order to get a JSON-LD markup describing your own resource using a Bioschemas profile
If have not read yet our how-to select the right profile for your resource, please give it a try before this one.

A pre-markup brainstorming activity

If you are eager to markup your resource, get your hands "coding" and quickly see some structured data rather that free text, you can skip this section and jump to the next one. However, if you want to go step by step and then smoothly move forward and get some JSON-LD for your resource, please stay here, you are on the right place.

Define your strategy

If your resource involves more than one profile, you first need to define the strategy that suits best to your case. You can link a profile, let's say DataCatalog, to other related ones, let's day Dataset, via properties. Sometimes those properties are bidirectional, so you can go from DataCatalog to Dataset or the other way around. Which direction suits best to you?
Link from DataCatalog to Dataset if you have some few datasets and you introduce them all on your catalog landing page. Example: UniProt
Link from Dataset to DataCatalog if you have that many datasets than rather than list them all, you provide a search and retrieval mechanism to find them. Example:

Map elements to properties

Now, focus on a particular profile, have at hand the corresponding specification page on Bioschemas as well as your resource, i.e., your web pages. Do a manual exercise mapping elements to properties. This will help you have a clearer idea on what you want to achieve once you go and use gimme-my-jsonld (see next section). You might need more than one iteration here as you can face multiple option at the beginning, choose that one that gives more benefits. Keep in mind your goal by adding this mark up to your resource.

Getting JSON-LD with gimme-my-jsonld

In progress