Hi Laura, Sorry for late response. Right now that is unquantified... We are engaged in ontology alignment activities such as https://github.com/ESIPFed/sweet/tree/master/alignments With other initiatives listed in our issue tracker https://github.com/ESIPFed/sweet/issues I 'was' going to try analyzing WebDataCommons to see if SWEET URI's were contained anywhere. http://www.webdatacommons.org/ I will say however, that SWEET is included in several OGC recommendations/standards. I am in the process of updating these documents to use the new http://sweetontology.net URI scheme. If you are interested in joining the community get us below https://github.com/ESIPFed/sweet#community
Lewis On 2018/03/07 06:20:15, "Laura Morales" <laure...@mail.com> wrote: > Sorry for the OT question but it's the first time I learn about SWEET. Is > there any list of datasets/graphs using this vocabulary? > Â > Â > > Sent:Â Wednesday, March 07, 2018 at 5:28 AM > From:Â "lewis john mcgibbney" <lewi...@apache.org> > To:Â users@jena.apache.org > Subject:Â OntModel.read parsing non-suffixed TTL as RDF/XML > Hi Folks, > > Over on the SWEET ontology suite [0] we recently changed out canonical > serialization to TTL. Additionally however, we removed all file suffixes > from the resources themselves, therefore although the following resource > [1] is serialized as TTL, you would never know unless you looked at it or > peeked into the server response. > > I am experiencing issues when I attempt to load the SWEET 'master' file > [2], which essentially produces a graph by importing every file within the > ontology suite. The code I use to do this is as follows. > > ((OntModel) m).read(url, null, lang); //Where lang is the string "TTL" or > "TURTLE" depending on previous logic. > > The stack trace I get is as follows [3] > > As you can see it loads the sweetAll file correctly but chokes on the > imported resource http://sweetontology.net/realmSoil, which is also a TTL > serialization but with no file suffix. The stack trace indicates that an > attempt is being made to parse the resource as RDF/XML... which in this > case is incorrect. > > Any hints on how to override/define this behaviour? > > Another related question, the large stack trace I receive from the above > parsing activity seems to also indicate that the OntModel.read logic > randomly processes imports when processing a resource such as [2]. Is this > correct? > > Thanks for any hits folks, I appreciate it. > Lewis > > [0] http://sweetontology.net[http://sweetontology.net] > [1] > http://sweetontology.net/reprDataProduct[http://sweetontology.net/reprDataProduct] > [2] http://sweetontology.net/sweetAll[http://sweetontology.net/sweetAll] > [3] https://paste.apache.org/vLt8[https://paste.apache.org/vLt8] > > -- > http://home.apache.org/~lewismc/[http://home.apache.org/~lewismc/] > http://people.apache.org/keys/committer/lewismc >
