J. Neil Otte

@mark-jensen 1. “All classes and properties are further required to have a textual definition, with a few exceptions.” —I think all classes and properties should have a textual definition, without...

@alanruttenberg Agreed. Posting a small discussion with reps from FIBO found in googling around on this topic: https://lists.w3.org/Archives/Public/semantic-web/2017Jul/0044.html May be of interest.

Strongly agree. The main argument for keeping English-readable labels in the IRI is that it makes it easier for developers to recognize a URI on sight. However, it only requires...

@rorudn What would be included in "the variety of different applications"? And are there known issues with opaque IDs that have been encountered with OnTop, Karma, or Ontotext? Given how...

@rorudn There's a comment at the bottom of[ this thread ](https://github.com/usc-isi-i2/Web-Karma/issues/217)indicating KARMA can display by rdfs:label. I'm not a regular KARMA user these days so can't verify this myself. Dave...

@mark-jensen 1. I suggest using hyphens in the local IDs rather than underscores. e.g. CCO-0000000, rather than CCO_0000000. This is a common best practice for URLs. 2. Recommend maintaining a...

Hey Mark, I’m getting a little confused between a) the characterization of cco:prescribes and b) best practice for using cco:prescribes. From your response, the following appears to be true: **If...

Hey Ron (thanks for jumping in here and happy holidays). To your first comment, I think that works in cases where I'm ingesting data about processes that have occurred, but...

By including '((x =w) or (x ≠w))', my intention was to convey that the DICE that prescribes the process and the DICE that prescribes the continuant that participates in the...

As a further case, see discussion of File Formats that prescribe Software Files here: https://github.com/CommonCoreOntology/CommonCoreOntologies/issues/29 The takeaway was that only if one wanted or needed to explicitly represent the process...