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

green-turtle

v0.0.0

Published

An RDFa 1.1 implementation in JavaScript for browsers.

Downloads

5

Readme

Green Turtle

An RDFa 1.1 implementation in JavaScript for browsers.

Note: This project has transitioned from its former Google Code project.

Conformance

Green Turtle passes all the tests for XML, XHTML1, XHTML5, HTML4, and HTML5 as provided by the RDFa WG except for the following notable issues:

  • XML Test 0332 uses a bare lang attribute instead of an xml:lang attribute. I believe this is a bug in the test. Green Turtle does the right thing with respect to xml:lang attributes in XML and lang attributes in HTML. A lang attribute in arbitrary XML has no special meaning.
  • XHTML1 Test 0198 and XHTML5 Test 0198 both have extra namespaces serialized in the XMLLiteral as expected output. The input for the test cases does not have XML namespace attributes. Instead, they use a prefix attribute to declare the prefixes used in the RDFa annotations. Meanwhile, when the literal is serialized, they are not in the in-scope namespaces. The RDFa specification says nothing about doing any kind of merging of prefixes and in-scope namespaces. I believe these test cases are incorrect. The correct serialization will not contain the rdf: and foaf: namespace declarations as they are not present in the source document.

I have submitted these issue to the working group for consideration.

Test Suite

To run the tests yourself, you will need Java and Ant installed and then do the following:

  1. Build Green Turtle by running ant in the root directory.

  2. Build the SPARQL service:

  3. Cache the test cases:

  4. Run the server:

  5. Visit http://localhost:8888/ in your browser.

  6. Select the markup language from the drop-down list box and hit the 'Test' button. The system will run the test cases rather silently unless you look at the console. Eventually, it will output a table of the status of all the test cases.

NPM package

An NPM package is in development. Right now it only exports a path to the build script so that it can be run within jsdom.

var greenTurtleScript = require('green-turtle')
  , jsdom = require('jsdom');

jsdom.env({
  file: 'test.html',
  scripts: [greenTurtleScript],
  done: function(err, window) {
    if (err) console.error(err);
    console.log(window.document.data.graph.toString());
  }
});