Closed nissimsan closed 2 weeks ago
@nissimsan , it needs to be merged in into the main branch. If you merge it into gs-pages, it will be lost within the next update pushed to main.
Also it is difficult to make it available on https://uncefact.github.io/untp-v1. GitHub pages doesn't support content negotiation. Can we use https://test.uncefact.org/vocabulary/untp/ domain instead? I can configure the deployment for it.
OK, @kshychko , new PR in place of this: https://github.com/uncefact/spec-untp/pull/108. Switching this to a draft PR, to be closed once 108 is closed.
I'll update the reference too to https://test.uncefact.org/vocabulary/untp/untp-v1
@nissimsan description
and name
need to be removed from the context as they are protected terms in vcdm v2. Please see this issue.
The example raises jsonld.SyntaxError: Invalid JSON-LD syntax; tried to redefine a protected term.
on the json-ld playground.
Here's the direction I was taking when drafting a context, it would be great to chat about this! https://ctx.traceability.site/untp/v0.json
@PatStLouis, I don't know what you are referring to, I'm not defining description
or name
.
This adds a limited LD context to the published pages. Should be available from
https://uncefact.github.io/untp-v1
.It is far from complete and must be further built out, potentially with tooling. Sharing this very early version is also meant to build the team's understanding of working with LD. This includes basing term definitions on UN in combination with other prevalent vocabs.
Obviously github.io is an unacceptable domain for any of what we do, not least our context.
Note it merges into
gh-pages
which probably also is not how we want to maintain in the long run.