<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[How To]]></title><description><![CDATA[Instructions on how to use the Mat-X componens ]]></description><link>https://community.mat-space.eu/category/5</link><generator>RSS for Node</generator><lastBuildDate>Wed, 10 Jun 2026 11:40:11 GMT</lastBuildDate><atom:link href="https://community.mat-space.eu/category/5.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 27 May 2026 19:14:50 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Ontology Curation - Github Sync]]></title><description><![CDATA[Concept
<p dir="auto">Each working ontology is stored as a <strong>public repository</strong> in the mds-ontologies organization. The canonical RDF file is ontology.ttl at the repo root. Fuseki holds the live graph; Git holds the versioned snapshot you commit and share. All kinds of ontology curation methods in MAT-X will use this.</p>
GitHub personal access token (fine-grained)
<p dir="auto">MAT-X uses a <strong>fine-grained</strong> token (not a classic token). You must be a member of mds-ontologies before it appears in the token wizard. An org admin can invite you under the organization's <strong>People</strong> tab on GitHub.</p>
<p dir="auto">Open github.com/settings/personal-access-tokens/new<br />
(or: your avatar -&gt; <strong>Settings</strong> -&gt; <strong>Developer settings</strong> -&gt; <strong>Personal access tokens</strong> -&gt; <strong>Fine-grained tokens</strong> -&gt; <strong>Generate new token</strong>).</p>
1) Token name and expiration
<p dir="auto">Choose any name (e.g. Mat-X ontology curation) and an expiration you are comfortable with. You can rotate the token later in Profile.</p>
2) Resource owner - this selects mds-ontologies
<p dir="auto">Under <strong>Resource owner</strong>, open the dropdown. You will see your personal GitHub username and, if you are a member, organizations such as mds-ontologies.</p>

Select <strong>mds-ontologies</strong>, not your personal username. The token is then scoped to that organization's repositories.
If mds-ontologies is missing, you are not a member yet - ask an org admin to add you, then refresh and restart the wizard.

3) Repository access
<p dir="auto">Choose <strong>All repositories</strong> (essential as otherwise the options below do not work). MAT-X creates a new public repo per working ontology (e.g. mds-ontologies/cement-model), so the token must cover repositories that do not exist yet.</p>
<p dir="auto"><strong>Only select repositories</strong> works only if you manually add every ontology repo to the token.</p>
4) Repository permissions
<p dir="auto">Set these permissions under <strong>Repository permissions</strong>:</p>

<strong>Contents</strong>: <strong>Read and write</strong> - clone, pull, commit, and push ontology.ttl.
<strong>Metadata</strong>: <strong>Read-only</strong> - usually required automatically.
<strong>Administration</strong>: <strong>Read and write</strong> - allows MAT-X to create new public repositories in mds-ontologies.
** Issues**: ** Read and write** allows MAT-X to create issues in case you are unhappy with developments

<p dir="auto">You do <strong>not</strong> Pull requests, Actions, or other permissions for ontology curation.</p>
5) Generate token and authorize SSO (if prompted)
<p dir="auto">Click <strong>Generate token</strong> and copy it immediately (GitHub shows it once). If your organization uses SAML SSO, go to Settings -&gt; Personal access tokens -&gt; Fine-grained tokens, find the new token, click <strong>Configure SSO</strong>, and authorize <strong>mds-ontologies</strong>.</p>
<p dir="auto">Without SSO authorization, API calls return 403.</p>
Save the token in MAT-X Profile
<p dir="auto">On the <strong>Profile</strong> page (/profile), add an API credential:</p>

Vendor: GitHub (or any label containing github)
API URL: https://api.github.com
API key: paste the fine-grained token

<p dir="auto">Keys are encrypted at rest with NEXTAUTH_SECRET. The server uses the first profile credential whose vendor or URL matches GitHub.</p>
Quick checklist
Resource owner:     mds-ontologies  (not your username)
Repository access:  All repositories
Contents:           Read and write
Metadata:           Read-only
Administration:     Read and write
Issues: Read and write 
SSO:                Authorized for mds-ontologies (if your org uses SAML)

]]></description><link>https://community.mat-space.eu/topic/3/ontology-curation-github-sync</link><guid isPermaLink="true">https://community.mat-space.eu/topic/3/ontology-curation-github-sync</guid><dc:creator><![CDATA[wenzel_int]]></dc:creator><pubDate>Wed, 27 May 2026 19:14:50 GMT</pubDate></item><item><title><![CDATA[Register for the MAT-X dataspace]]></title><description><![CDATA[Register for the Mat-X dataspace
<p dir="auto">blaha</p>
]]></description><link>https://community.mat-space.eu/topic/2/register-for-the-mat-x-dataspace</link><guid isPermaLink="true">https://community.mat-space.eu/topic/2/register-for-the-mat-x-dataspace</guid><dc:creator><![CDATA[wenzel_int]]></dc:creator><pubDate>Tue, 26 May 2026 21:02:32 GMT</pubDate></item></channel></rss>