Merge pull request #942 from semanticarts/release/12.0.1

Release 12.0.1 (into `master`)

Author: rjyounes

README.md

@@ -5,13 +5,13 @@ About gist
 
 gist is Semantic Arts' minimalist upper ontology for the enterprise. It is designed to have the maximum coverage of typical business ontology concepts with the fewest number of primitives and the least amount of ambiguity.
 
-We have an active governance and best practices community around gist called the gist Council, with a teleconference on the first Thursday of every month, where practitioners and users of gist come together to discuss how to use gist and make suggestions on its evolution.  Please send email to [GistCouncil@semanticarts.com](mailto:GistCouncil@semanticarts.com) if you would like to become involved.
+We maintain an active gist community forum where developers and users of gist come together to discuss the gist model, implementation best practices, and the evolution of gist. Meetings occur virtually on the first Thursday of every other month, starting in January. Please send email to [GistForum@semanticarts.com](mailto:GistForum@semanticarts.com) if you would like to become involved.
 
 You can also contribute to gist by adding your comments to [issue discussion threads](https://github.com/semanticarts/gist/issues) and submitting new issues and pull requests (see [guidelines for contributions](https://github.com/semanticarts/gist/blob/master/docs/Contributing.md)). You can view [minutes](https://github.com/semanticarts/gist/wiki/gist-Development-Team-Meeting-Notes) from our bi-monthly review sessions to find out what we've been discussing and get a preview of upcoming changes to gist.
 
 gist is free and open to the public under the [Creative Commons 3.0](http://creativecommons.org/licenses/by-sa/3.0/) attribution share-alike license. In addition to the conditions of this license, we require that any concepts used from gist remain in the gist namespace, and that you do not define your own term definitions in the gist namespace.
 
-For more information on gist and to download previously released versions of gist, see the [Semantic Arts website](https://www.semanticarts.com/gist).
+For more information on gist and to download the current or previous versions of gist, see the [Semantic Arts website](https://www.semanticarts.com/gist).
 
 Documentation
 -----

bundle.yaml

@@ -94,7 +94,10 @@ actions:
     from: "(.*)\\.ttl"
     to: "\\g<1>{version}.ttl"
   includes:
-    - "*.ttl"
+    - gistCore.ttl
+    - gistMediaTypes.ttl
+    - gistPrefixDeclarations.ttl
+    - gistSubClassAssertions.ttl
 - action: "definedBy"
   message: "Adding rdfs:isDefinedBy."
   source: "{output}"

docs/Namespace.md

@@ -17,8 +17,8 @@ available, that cover extensions to this core, both horizontally (HR and
 Accounting) and vertically (Professional Services, Healthcare). These
 other ontologies have different names but share the gist namespace.
 
-If you’re wondering why the namespace isn’t the same as the ontology IRI,
-and therefore why it didn’t return the ontology, read on.
+If you're wondering why the namespace isn't the same as the ontology IRI,
+and therefore why it didn't return the ontology, read on.
 
 The Difference Between Namespaces and Ontologies
 -----
@@ -30,7 +30,7 @@ historically contained in a file.
 
 The reason these two terms are so often conflated is that most ontology
 editing tools will provide both as a convenient default and will make both
-the same. When you’re just screwing around learning ontology authoring
+the same. When you're just screwing around learning ontology authoring
 and building toy apps, this collapsing of the two terms is mostly benign.
 
 It turns out that applying this default behavior to production systems is
@@ -57,7 +57,7 @@ you meant the default, which by default is the name of the ontology
 itself. This is the root of the confusion.
 
 We advocate not using a default namespace. Much better to be explicit,
-and as we’ll see, explicitness encourages (or at least doesn’t obscure)
+and as we'll see, explicitness encourages (or at least doesn't obscure)
 reusing other terms that may have been minted elsewhere.
 
 Minting IRIs
@@ -66,8 +66,8 @@ Minting IRIs
 The person or system that first defines a term or creates an identifier
 for a real world instance is said to have "minted" the identifier. It
 mints it within a namespace. It should be a namespace you have
-control over. Minting an IRI in someone else’s namespace is called
-"namespace squatting." Not only is it poor form, it doesn’t really
+control over. Minting an IRI in someone else's namespace is called
+"namespace squatting." Not only is it poor form, it doesn't really
 accomplish anything. If you decide to mint an IRI in the gist
 namespace, no one else will know this happened. You will be shouting
 in a well.
@@ -85,7 +85,7 @@ This is essentially a path within the domain name `w3id.org`, whose owners
 have given us exclusive control over. When we mint new terms, we will do so
 in this namespace.
 
-An ontology needn’t have any IRIs minted it its "own" namespace
+An ontology needn't have any IRIs minted it its "own" namespace
 -----
 
 To cement the idea that the ontology need not have a 1:1 coorespondence to
@@ -106,15 +106,15 @@ its namespace, consider the following legitimate ontology.
 ```
 
 The first 8 lines declare namespace prefixes. Strictly speaking they are
-just conveniences (abbreviations), so that line 11 doesn’t get too long
+just conveniences (abbreviations), so that line 11 doesn't get too long
 to read. The name of the ontology is in line 10. The entire ontology is
-in line 11, and doesn’t refer to anything that was minted in this ontology.
+in line 11, and doesn't refer to anything that was minted in this ontology.
 It just says that someone named mccomb (as per the Semantic Arts
-namespace) owns (as per gist’s definition of ownership) something
+namespace) owns (as per gist's definition of ownership) something
 that dbPedia will soon recognize as Semantic Arts.
 
 This ontology does not have any IRIs minted in either its namespace
-(which isn’t even declared; I took out the default declaration) or
+(which isn't even declared; I took out the default declaration) or
 in this ontology.
 
 How to partition
@@ -141,15 +141,15 @@ with the other two.
 Governance drives namespace use
 -----
 
-But just because you’ve divided your ontology into partitions (modules)
-doesn’t mean the namespaces must follow. In the above example, if one
+But just because you've divided your ontology into partitions (modules)
+doesn't mean the namespaces must follow. In the above example, if one
 group were doing all the ontology work for vendor, material and purchasing,
 they could easily do all three in the same namespace.
 
 You really only need separate namespaces if you have people minting
 terms that are not coordinating with each other. If you have one group
 minting the term: `Account` to mean what accountants think and the
-sales group minting the term `Account` to mean prospect, you’d have
+sales group minting the term `Account` to mean prospect, you'd have
 a difficult time with the accidental term collisions.
 
 The solution is either to coordinate, or to have separate namespaces.
@@ -173,7 +173,7 @@ The problems become more obvious the more files you have. If someone
 mints a term, say a property or a class, in a sub-ontology that everyone
 agrees would be useful to have in other sub-ontologies, the other
 sub-ontologies can either import the one with the term they want
-(getting a bunch of axioms they don’t want) or they can lobby for
+(getting a bunch of axioms they don't want) or they can lobby for
 promoting the term to a higher level ontology where it can be reused
 more easily. The only problem is that with that promotion, because
 each ontology has its own namespace, the name of the term must be

docs/ReleaseNotes.md

@@ -1,6 +1,23 @@
 gist Release Notes
 =====
 
+Release 12.0.1
+-----
+
+### Patch Updates
+
+- Added missing `owl:Thing` assertions to gist instances to ensure that `rdfs:isDefinedBy` assertions are generated during the release bundling process. Issue [#775](https://github.com/semanticarts/gist/issues/775).
+
+- Updated description of gist Forum in README. Issue [#917](https://github.com/semanticarts/gist/issues/917).
+
+- Changed smart single quotes to straight quotes for the apostrophes in `docs/Namespace.md`. Issue [#919](https://github.com/semanticarts/gist/issues/919).
+  
+- Updated `bundle.yaml` to exclude the `gistValidationAnnotations` ontology from the release package. Issue [#922](https://github.com/semanticarts/gist/issues/922).
+
+- Updated the Python HTML renderer to fix errors in display of gist documentation in the browser. Issue [#923](https://github.com/semanticarts/gist/issues/923).
+
+Import URL: <https://w3id.org/semanticarts/ontology/gistCore12.0.1>.
+
 Release 12.0.0
 -----
 
@@ -15,6 +32,7 @@ This is a major release which includes several changes which break compatibility
   - For each pair of inverses, the property deemed clearest, simplest, and/or most useful was retained.
   - Axioms referring to the deleted properties were reformulated using `owl:inverseOf`.  
   - Breakdown:
+
       | Properties retained in gist | Inverse properties removed from gist |
       | ----------- | ----------- |
       `hasDirectPart` | `isDirectPartOf`

gistCore.ttl

@@ -2608,7 +2608,10 @@ gist:_candela
 	.
 
 gist:_day
-	a gist:DurationUnit ;
+	a
+		owl:Thing ,
+		gist:DurationUnit
+		;
 	skos:definition "A duration unit that is 24 hours long."^^xsd:string ;
 	skos:prefLabel "day"^^xsd:string ;
 	gist:conversionFactor "86400.0"^^xsd:double ;
@@ -2664,7 +2667,10 @@ gist:_meter
 	.
 
 gist:_millisecond
-	a gist:DurationUnit ;
+	a
+		owl:Thing ,
+		gist:DurationUnit
+		;
 	skos:definition "A unit equal to a thousandth of a second."^^xsd:string ;
 	skos:prefLabel "millisecond"^^xsd:string ;
 	gist:conversionFactor "0.001"^^xsd:double ;
@@ -2673,7 +2679,10 @@ gist:_millisecond
 	.
 
 gist:_minute
-	a gist:DurationUnit ;
+	a
+		owl:Thing ,
+		gist:DurationUnit
+		;
 	skos:definition "A unit equal to 60 seconds."^^xsd:string ;
 	skos:prefLabel "minute"^^xsd:string ;
 	gist:conversionFactor "60.0"^^xsd:double ;

gistSubClassAssertions.ttl

@@ -12,7 +12,7 @@
 	owl:imports <https://w3id.org/semanticarts/ontology/gistCore> ;
 	skos:definition "Supplementary subclass assertions for gistCore."^^xsd:string ;
 	skos:prefLabel "gist Subclass Assertions"^^xsd:string ;
-	skos:scopeNote "This ontology contains supplementary subclass assertions that are logically entailed by gistCore but are not inferred by some automated reasoners. For example, an OWL RL reasoner would not infer that gist:Commitment is a subclass of gist:Intention, even though it follows from the ontology axioms. More precisely, it contains (1) subclass assertions derived using an OWL DL reasoner and (2) the subclass assertions that are already explicit in gistCore."^^xsd:string ;
+	skos:scopeNote "This ontology contains supplementary subclass assertions that are logically entailed by gistCore but are not inferred by some automated reasoners. For example, an OWL RL reasoner would not infer that gist:Commitment is a subclass of gist:Intention, although it follows from the ontology axioms. More precisely, it contains (1) subclass assertions derived using an OWL DL reasoner and (2) the subclass assertions that are already explicit in gistCore."^^xsd:string ;
 	gist:license "https://creativecommons.org/licenses/by-sa/3.0/"^^xsd:string ;
 	.