I was looking at the https://github.com/ESIPFed/sweet/blob/master/README.md page (the landing page for https://sweetontology.xxx IRIs) and realized it did not point users to an actual ontology, in case they wanted to view it. (There is a pointer to how resolution happens, but that's a hopelessly geeky description that doesn't help users find a view of the ontology.)
I was going to add the following:
If you want to browse the SWEET ontology, visit http://sweetontology.net/sweetAll, which
but I got stuck because http://sweetontology.net/sweetAll doesn't show triples right now (#174). Based on Carlos' response to #174, I think the metadata for sweetAll (#175) needs to describe why no triples are visible for the ontology, and where to go to find its triples, and how to search within all the SWEET triples.
It also occurs to me that linking to SWEET in the various repositories in which it lives might be elegant. But COR should definitely get top billing. (Even if not importing the imports is not a particularly standard practice in my experience.)
I was looking at the https://github.com/ESIPFed/sweet/blob/master/README.md page (the landing page for https://sweetontology.xxx IRIs) and realized it did not point users to an actual ontology, in case they wanted to view it. (There is a pointer to how resolution happens, but that's a hopelessly geeky description that doesn't help users find a view of the ontology.)
I was going to add the following:
but I got stuck because http://sweetontology.net/sweetAll doesn't show triples right now (#174). Based on Carlos' response to #174, I think the metadata for sweetAll (#175) needs to describe why no triples are visible for the ontology, and where to go to find its triples, and how to search within all the SWEET triples.
It also occurs to me that linking to SWEET in the various repositories in which it lives might be elegant. But COR should definitely get top billing. (Even if not importing the imports is not a particularly standard practice in my experience.)