npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

shaclc-write

v1.4.3

Published

A writer for SHACLC documents

Downloads

8,495

Readme

shaclc-writer

Write RDF/JS quads to SHACLC documents

Usage

import { Parser } from 'n3';
import { write } from 'shaclc-write';

const ttl = `
@base <http://example.org/array-in> .
@prefix ex: <http://example.org/test#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<>
	a owl:Ontology ;
.

ex:TestShape
	a sh:NodeShape ;
	sh:property [
		sh:path ex:property ;
		sh:in ( ex:Instance1 true "string" 42 ) ;
	] ;
.
`

async function main() {
  const quads = (new Parser()).parse(ttl);

  const { text } = await write(quads, {
    prefixes: {
      ex: "http://example.org/test#",
      sh: "http://www.w3.org/ns/shacl#",
      owl: "http://www.w3.org/2002/07/owl#"
    }
  });


  // BASE <http://example.org/array-in>
  // PREFIX ex: <http://example.org/test#>
  //
  // shape ex:TestShape {
  // 	ex:property in=[ex:Instance1 true "string" 42] .
  // }
  console.log(text)
}

main();

Identifying quads that could not be serialized

By default an error is thrown if there are quads that cannot be serialised in SHACLC. Alternatively we can skip throwing errors and just return the quads that cannot be serialised.

import { Parser } from 'n3';
import { write } from 'shaclc-write';

const ttl = `
@base <http://example.org/array-in> .
@prefix ex: <http://example.org/test#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<>
	a owl:Ontology ;
.

ex:TestShape
	a sh:NodeShape ;
	sh:property [
		sh:path ex:property ;
		sh:in ( ex:Instance1 true "string" 42 ) ;
	] ;
.

ex:Jesse ex:knows ex:Bob .

`

async function main() {
  const quads = (new Parser()).parse(ttl);

  const { text, extraQuads } = await write(quads, {
    prefixes: {
      ex: "http://example.org/test#",
      sh: "http://www.w3.org/ns/shacl#",
      owl: "http://www.w3.org/2002/07/owl#"
    },
    errorOnUnused: false
  });


  // BASE <http://example.org/array-in>
  // PREFIX ex: <http://example.org/test#>
  //
  // shape ex:TestShape {
  // 	ex:property in=[ex:Instance1 true "string" 42] .
  // }
  console.log(text)

  // Array containing a single RDF/JS representing the triple "ex:Jesse ex:knows ex:Bob"
  console.log(extraQuads)
}

main();

Minting prefixes

Prefixes for namespaces that have not been specified can also be created on demand (first it attempts to look up a prefix on prefix.cc and will generate one if this fails).

async function main() {
  const quads = (new Parser()).parse(ttl);

  const { text } = await write(quads, {
    mintPrefixes: true,
  });


  // BASE <http://example.org/array-in>
  // PREFIX test: <http://example.org/test#>
  //
  // shape test:TestShape {
  // 	test:property in=[test:Instance1 true "string" 42] .
  // }
  console.log(text)

  // Array containing a single RDF/JS representing the triple "ex:Jesse ex:knows ex:Bob"
  console.log(extraQuads)
}

main();

Extended SHACL Compact Syntax

The SHACL Compact Syntax specification is not expressive enough to make any RDF 1.0 statement. This package includes an opt-in extended syntax that allows users to make any RDF 1.0 statement. Writing of this extended syntax can be enabled via an option in the write function

const quads = write(/*quads*/, { extendedSyntax: true })

Making additional statements about the NodeShape

Additional statements can be made about NodeShapes by using a turtle-like syntax before the body of the shape. For instance we can add the following statements to the above ex:TestShape.

ex:TestShape ex:myCustomAnnotation ex:myCustomValue ;
	ex:myCustomBlankNodeAnnotation [
		ex:myCustomList ( 1 ex:myCustomValue )
	] .

by doing the following:

shape ex:TestShape -> ex:TestClass1 ex:TestClass2 ;
	ex:myCustomAnnotation ex:myCustomValue ;
	ex:myCustomBlankNodeAnnotation [
		ex:myCustomList ( 1 ex:myCustomValue )
	] {
		targetNode=ex:TestNode targetSubjectsOf=ex:subjectProperty targetObjectsOf=ex:objectProperty .
	}

Making additional statements about the sh:property

additional statements can be made about each blank node property as follows:

shape ex:TestShape -> ex:TestClass1 ex:TestClass2 {
	ex:myPath [0..1] %
		ex:myCustomPropertyAnnotation ex:myCustomPropertyValue ;
		ex:myCustomPropertyAnnotation2 ex:myCustomPropertyValue2 ;
	% .
}

Making arbitrary statements

Finally we permit the use of turtle syntax at the end of the file to make any additional statements

shape ex:TestShape -> ex:TestClass1 ex:TestClass2 {
	targetNode=ex:TestNode targetSubjectsOf=ex:subjectProperty targetObjectsOf=ex:objectProperty .
}

ex:bob a ex:Person .