Hi there.

hey I'm building a very comprehensive seo plugin for wordpress. And I absolutely love this git. So with that said. Ive' been researching new ontologies and specifically GS1 since they've been recognized by schema and W3. But they are not registered on http://dbpedia.org/sparql?nsdecl. But heres what I got for your reference.

https://www.gs1.org/standards/gs1-source/guideline/gs1-source-tsd-technical-implementation-guide-aggregators

https://www.gs1.org/edi-xml/technical-user-guide/Schema_hierarchy

https://www.gs1.se/en/our-standards/Technical-documentation/code-lists/
https://www.gs1.se/esap/20tradeitem/ver285/gu1.htm
https://www.gs1.se/esap/20tradeitem/ver285/gu5.htm
https://github.com/mobilemadman2/gs1

Overlapping prefixes are not handled as expected (original issue zazuko/SPEX#20).

The following test doesn't pass:

it('handles overlapping prefixes', () => {
  prefixes['foo'] = 'http://example.com/foo/'
  prefixes['bar'] = 'http://example.com/foo/bar/'

  expect(shrink('http://example.com/foo/test')).toBe('foo:test')
  expect(shrink('http://example.com/foo/bar/test')).toBe('bar:test')
})

Note that it works if the prefixes are added in reverse order:

prefixes['bar'] = 'http://example.com/foo/bar/'
prefixes['foo'] = 'http://example.com/foo/'

Evaluate what it means to integrate the various QUDT schemas and ontologies.

• http://www.linkedmodel.org/catalog/qudt/1.1/index.html
• http://www.qudt.org/release2/qudt-catalog.html

Questions:

• are there clashes between the two versions?
• why are they split among files even though there seems to be only one namespace used?
• what namespaces & files should be sourced?

http://www.w3.org/ns/rdfa#

And while we are at it, vann: http://vocab.org/vann/

I would like to be able to use this package's functionality in the browser. Currently the biggest obstacle is using node.js filesystem APIs (fs and path).

I propose to split the ontology code from the loading code so that it can be substituted with different code for the browser. I have two ideas:

1. Simpler, to use fetch. The problem here is that the files have to be fetched from somewhere. Either raw.github URLs or manually added to the deployed app.
2. Use dynamic imports, which forces some additional effort on the consumer to set up webpack or similar to handle

Apparently we get blocked fast by w3c.org while fetching the data. @vhf how fast/when does it happen? Maybe @iherman can help us out here.

Ivan, we fetch RDF vocabularies in an automated way every few months and add the latest RDF versions of it in this repository. That seems to be enough to get the IP blocked by W3C for a while.

Dereferencable here: http://www.w3.org/2003/06/sw-vocab-status/ns#

Is it any popular? Hydra uses it to annotate its terms.

additionally, I'm thinking that the prefix server could actually take advantage of this and/or similar annotations to highlight deprecated terms

Thanks for great work.

It would be great if ontologies folder itself is available as separate git repository. We can still include it as a folder for all practical purposes using git-sub-modules. This will enable to include same stack-agnostic ontologies in any repository with any language stack.

Used in Swisstopo dataset:

@prefix gn: <http://www.geonames.org/ontology#> .

RDF Ontology: http://www.geonames.org/ontology/ontology_v3.1.rdf

See https://twitter.com/philarcher1/status/1446501549296001025

QUDT is missing from LOV: https://lov.linkeddata.es/dataset/lov/terms?q=qudt. If as part of #13 you dig through the structure of QUDT, it would be great if you submit it properly to LOV.

I just saw this on Bart's demo: https://www.w3.org/ns/locn

I see that we don't have this one

buildPath is returning node_modules/@zazuko/ontologies instead of the correct node_modules/@zazuko/rdf-vocabularies/ontologies.

Additionally, the vocabularies() function should properly throw an error if it reads files in the wrong location.

Thanks for this tool!

There is a link to the RDF/OWL here https://tech.ebu.ch/MetadataEbuCore

Spec: https://semanticweb.cs.vu.nl/2009/11/sem/
Prefix: sem
Namespace: http://semanticweb.cs.vu.nl/2009/11/sem/

According to schemaorg/schemaorg#2304 (comment) the download location here:

Might change. We need to keep an eye on that issue.

Issues in current namespace list:

• duv: NS should be http://www.w3.org/ns/duv# according to ontology but different in RDFa initial context, I guess it simply points to the HTML spec
• dc & dcterms point to the same URI. We should settle on one
• dbpedia points to resource and ontology, should be resource IMO

Namaste all. It is a request for few vocabularies. These are mainly used for implementing solid specifications. These all vocabs have prefix.cc registered prefixes, and ther namespace base iri de-references to their ontology files

Thanks again for your work

Those prefixes & namespaces are defined in RDFa initial context but are missing in action, or at least an RDF version of them is. Please comment if you find any of them.

• ctag:
• gml:
• rev:
• rif:
• sf:
• v:
• xml:

Hi zazuko team - is it possible to include the metadata4ing ontology in your prefix lookup service? You can find details on the ontology here:

http://metadata4ing.org

Serializations in different formats are also available via that link.

Thanks and kind regards, Marc

Do we want to rename dc11 to dc?

https://www.dublincore.org/specifications/bibo/bibo/

I just got this idea to extract the code used to generate this package contents (index, etc.) as well as the generator of @tpluscode/rdf-ns-builders

This would allow others to create their own similar packages for other ontologies which we might not want to incorporate in this list for some reason.

Originally posted by @tpluscode in #55 (comment)

It looks like SIOC is skipped but I find it in ontologies?

@zazuko/rdf-vocabularies is quite large (nearly 20MB). tpluscode/rdf-ns-builders@3019d71 was committed to avoid forcing this as a runtime dependency, but there are still cases where it would be useful to have a simple library containing just prefixes.js to avoid having to hard-code the IRIs elsewhere (eg libero/article-store#260 (comment)).

Would it be possible to extract this into its own package? (@zazuko/rdf-vocabulary-prefixes or something?)

The vocabulary should use http URLs but we have https

Good idea via @semanticfire, we should add two more quads to each vocabulary dump to describe the prefix & namespace we use for it.

Bart proposed using vann but I can't seem to fetch an RDF version of it anymore, the links are dead.

Ivan is using the RDFa vocabulary for this, see for example here. So my proposal would be to add these two quads using the RDFa vocabulary.

Via @iherman I got links to the following RDF resources, taken from his mail:

• as: https://www.w3.org/ns/activitystreams-owl.ttl
• ical: http://www.w3.org/2002/12/cal/icaltzd.rdf (it downloads the RDF/XML file in most browsers instead of displaying it)
• xhv: http://tinyurl.com/yy4pbocc (the vocabulary is in the HTML file in RDFa, and this URL runs the RDFa distiller to return the turtle file)

Those should be sourced as well

Turtle: https://github.com/linked-statistics/xkos/blob/master/xkos.ttl

When the @zazuko/rdf-vocabularies/expand module is imported in a web project, webpack will try to create chunks for all the vocabularies because the expandWithCheck is dynamically loaded and it pull the n-quad sources.

With raw-loader added the bundle sizes explode.

Probably the only way would be to separate the expand and expandWithCheck modules. What do you think @vhf?

Dear zazuko team,

there is a new release for Metadata4Ing: https://w3id.org/nfdi4ing/metadata4ing/1.2.0/

We wanted to let you know and ask whether you could update here/ for the zazuko prefix service.

Thank you and all the best form the m4i working group

Susanne

The one big namespace missing is XSD, which seems surprisingly hard to get. I asked around on Twitter here and after an interesting thread @gkellogg pointed to some work he did here.

This should be added to overrides.js

See https://www.w3.org/2003/12/exif/

Schema (RDF/XML) is here: http://www.w3.org/2003/12/exif/ns

More information: http://www.sparontologies.net/ontologies/frbr

Somehow we completely missed SHACL

https://www.w3.org/TR/shacl/

I thought we might add prefixes for the non-vocabulary DBpedia namespaces:

{
  "dbr": "http://dbpedia.org/resource/",
  "yago": "http://dbpedia.org/class/yago/",
  "yago-res": "http://yago-knowledge.org/resource/"
}

Not too sure about the YAGO stuff though...

More info & namespace: http://www.rdaregistry.info/Elements/u/#

https://dublincore.org/specifications/dublin-core/dcmi-terms/

This:

Should be

http://www.ebu.ch/metadata/ontologies/ebucore/ebucore#

Spec:

https://www.w3.org/TR/HTTP-in-RDF10/

content-neg seems to work

http://purl.org/linked-data/sdmx#

Requirements

• Opinionated list of prefixes, and namespaces independently available.
• Opinionated list of snapshotted ntriple dumps, and their definition how it was fetched on their (original) source.
• Optional (added) metadata on the used meta-ontology and its used annotations (rdfs:label vs. schema:name). (RDFS/OWL etc.)

JS Requirements

• Opinionated map of prefixes, and namespaces independently available.
• Opinionated list of snapshotted transformed to RDF/JS quads.
• Defined package structure / define ontologies in a NPM package.

Implementation

• Ontology package -> annotation (prefix, how to get it) -> tiny (<5kb) (as Turtle) [authorative source]

  • updates JS prefix map (transformation)
  • publishes a NPM package with the JS prefix maps

• Snapshots package -> uses the Ontology package

  • fetches (on the web) the snapshotted ntriple dumps (gzipped)
  • publishes a NPM package with the RDF-JS quads versions (only)
    • define an interface that covers the quads and metadata for external people to create compatible ontology packages