profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/semanticarts/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

semanticarts/gist 67

gist upper enterprise ontology

semanticarts/ontology-toolkit 16

Tools to update and export ontology RDF.

semanticarts/shacl-validator 2

Node.js SHACL Valdiator

semanticarts/airquality 1

A demonstration of using Node-RED, RDFox and Raspberry Pi to gather and condense air sensor data

semanticarts/ontodoc 1

A static documentation generator for OWL ontologies

semanticarts/pytarql 1

Python implementation of TARQL

semanticarts/csv-summary 0

Generates a basic analysis of a CSV to an XLSX workbook.

semanticarts/dcaf2021-shacl-workshop 0

Materials for Steve Steward's workshop at DCAF 2021

semanticarts/gistGeo 0

An extension to the gist ontology supplemented with some ABox data

semanticarts/OntoUtils 0

useful utilities that can be used with ontologies

issue commentsemanticarts/gist

Review and refactor :hasTag and other text datatype properties

Note that the property has already been renamed to tagText - other issues to be discussed and should be considered in relation to #594.

DanCarey404

comment created time in 8 hours

issue commentsemanticarts/gist

Broaden the range of containedText to include xsd:anyURL for representing web addresses.

Makes sense. Consider in conjunction with #372.

uscholdm

comment created time in 8 hours

issue openedsemanticarts/gist

Broaden the range of containedText to include xsd:anyurl for representing web addresses.

I want to create a class, WebAddress as follows:

ibbeo:WebAddress
    a owl:Class ;
    skos:prefLabel "Web Address"^^xsd:string ;
    skos:definition "A URL"^^xsd:string ;
    rdfs:subClassOf
      gist:Address ,
      [
        a owl:Restriction ;
        owl:onProperty gist:containedText ;
        owl:someValuesFrom xsd:anyurl ;
      ]
      ;
      .

But the property containedText has range xsd:string

gist:containedText
	a owl:DatatypeProperty ;
	rdfs:range xsd:string ;
	skos:definition "Links to the string corresponding to Text"^^xsd:string ;
	skos:prefLabel "contained text"^^xsd:string ;
	.

Althought gist:containedText was created specifically for use with gist:Text, it has no domain, so it should be usable with anything that corresponds to text, which is the case for a WebAddress.

created time in a day

issue openedsemanticarts/gist

Add dct:license

Minor request, the website https://archivo.dbpedia.org/rating gives stars to ontology ratings based on having this property point to a URI, and preferably to a resolvable license.

★ License (I & II)

The second and third star are granted for proper and clear license statements and are tested with the Archivo SHACL Library.

License I grants a star for a huge variety of license statements, i.e. when a license is given, but consumers need to spend extra integration effort to understand and use it (cf. License I SHACL test).

License II grants a star for a homogenized license statement: 1. using the property dct:license and a URI as object. (cf. License II SHACL test). 

Dave said we should add it.

created time in a day

issue commentsemanticarts/gist

question: relationship between gist:hasPart and gist:isMadeUpOf

Now we getting into process irrreversibility as the definition of absorbtion into the whole." Very interesting!

justin2004

comment created time in a day

issue commentsemanticarts/gist

question: relationship between gist:hasPart and gist:isMadeUpOf

OK, since I'm not a chemist, let's go with the flour/cake example.

justin2004

comment created time in a day

issue commentsemanticarts/gist

question: relationship between gist:hasPart and gist:isMadeUpOf

Hi @rjyounes ,

in that the latter retains its independent identity whereas the former don't, becoming absorbed into the whole.

If the definition of "retention of independent identity" is something like: "the part can be extracted from the whole without destroying the part" then the relationship of hydrogen to water meets the same criteria as the engine block to a spark plug.

I can remove the spark plug from the engine block with a torsional force and the spark plug is still a spark plug. I can remove the hydrogen from the water with electrolysis and the hydrogen is still hydrogen.

(Though that does make me think a useful test for direct parts might be whether or not you can remove them from the whole and the whole still exists.)

The torsional force is macroscopic chemistry and the electrolysis is microscopic chemistry. But the macro/micro distinction there is an example of what Dennett calls "scale chauvinism."

If instead the definition of "retention of independent identity" isn't about the ability to extract the parts but more about the absorption into the whole... I still don't think I still much difference between an engine doings its thing with all of its parts and water doing its thing with all of its parts... other than the role of gist:Artifact. But maybe my world hypothesis is mechanism and gist's is another.

(I'm treating spark plug as a direct part of an engine block just for this discussion but I think it isn't.)

justin2004

comment created time in 2 days

issue commentsemanticarts/gist

question: gist:hasDirectPart scope note

You're absolutely right that hasDirectPart is tricky, for the reason you mention. You may want to review the closed issues #115 and #328 to see our general discussions on the hasDirectX pattern.

justin2004

comment created time in 2 days

issue commentsemanticarts/gist

question: relationship between gist:hasPart and gist:isMadeUpOf

There is no intent that thehasPart relationship be limited to Artifacts. The real issue is that there are many types of whole-part relationships, and we plan to dig into this and distinguish the different kinds. As one example, the relationship of hydrogen to water, or flour to a cake, is quite different from the relationship of a spark plug to an engine block, in that the latter retains its independent identity whereas the former don't, becoming absorbed into the whole. It's an open question whether we will have one super-property of all of these various whole-part relationships or not.

justin2004

comment created time in 2 days

issue commentsemanticarts/gist

question: gist:hasDirectPart scope note

My dad proposed that a "coolant passage" is a direct part of an engine block. :)

Though "coolant passage" is a component of the cooling system.

justin2004

comment created time in 2 days

issue openedsemanticarts/gist

question: relationship between gist:hasPart and gist:isMadeUpOf

It seems like gist should assert that:

gist:isMadeUpOf rdfs:subPropertyOf gist:hasPart .

Being made up of something is a specialization of being a part of something. Water is made up of hydrogen and hydrogen is part of water.

If we don't think gist should assert that then that might mean gist intends gist:hasPart to be a relationship between gist:Artifacts only -- since water and hydrogen are not gist:Artifacts. But I don't think that is necessary because it is easy to find that out in a query:

select * where {
?s gist:hasPart ?o .
?o a gist:Artifact .
?s a gist:Artifact .
}

A bit of background here... I am working on getting water quality data into Wikidata (my example entity is here). I am using wdt:hasPart to related drinking water to things in it (such as copper, lead, etc.). And eventually I'd like to put more effort into aligning Wikidata with Gist.

created time in 2 days

issue openedsemanticarts/gist

question: gist:hasDirectPart scope note

"For example, a spark plug is a direct part of an engine block; there cannot be any intermediate parts." https://github.com/semanticarts/gist/blob/7513770f22780edfeef17789d826daeed3d7d7b7/gistCore.ttl#L3166

I think this example relies on the close proximity between a spark plug and and engine block. There are no intervening parts. They are directly adjacent. But there are many other parts of an engine that directly touch (and are mounted onto) the engine block that aren't direct parts of the engine block. An engine block is an assemblage of machined pieces of metal. e.g An exhaust manifold is a component in the exhaust system. An oil pump is a component in the lubrication system and also the cooling system.

And a spark plug is a component in the ignition system.

I think gist:hasDirectPart is tricky because we can often find a sub-system that slips in between directly adjacent (physically) components.

Can we find some better examples of direct parts?

created time in 2 days

startedsemanticarts/gist

started time in 2 days

issue commentsemanticarts/gist

Address issues with gist:Task and gist:ScheduledTask

OK, but is that really a useful distinction? Do we need to know that a task now completed was or wasn't scheduled? Can you describe a context in which that distinction would be important?

turingtest37

comment created time in 3 days

issue commentsemanticarts/gist

Address issues with gist:Task and gist:ScheduledTask

In the current hierarchy I don't see a difference between Task and ScheduledTask, defined as "A task planned to occur. When it was scheduled, it would have been in the future, but now might be in the past." Isn't that the same as "A task which has been defined and either scheduled or accomplished, or both."?

The difference is that "A task which has been defined and either scheduled or accomplished, or both." might not have been scheduled. A ScheduledTask by definition is or was scheduled.

turingtest37

comment created time in 3 days

issue closedsemanticarts/ontology-toolkit

Display instance counts as size in graphic --data

Also, line thickness should scale with the --instance-limit value, with max count resulting in the max width (currently 5)

closed time in 3 days

sa-bpelakh

issue commentsemanticarts/ontology-toolkit

Display instance counts as size in graphic --data

Implemented in #81

sa-bpelakh

comment created time in 3 days

issue commentsemanticarts/gist

Circular definition of Task

Hm, I see. I didn't look at gist when I responded. So the definition as it stands actually means: The event of performing a task in the usual sense and thus the apparent circularity!

I think it's a stretch to call tasks and projects events, and it's unfortunate that they are defined as such. It would be good to find out if that's how people are using it.

In the current hierarchy I don't see a difference between Task and ScheduledTask, defined as "A task planned to occur. When it was scheduled, it would have been in the future, but now might be in the past." Isn't that the same as "A task which has been defined and either scheduled or accomplished, or both."?

There's a lot that's fishy here and I think we should work out what classes are actually needed. I'd consider a Tasksubclass of Intention, and a ScheduledTask that is the intersection of Task and PlannedEvent, as currently.

I'm going to change the title of this issue to reflect the fact that it's more than a matter of the text definition.

turingtest37

comment created time in 4 days

created tagsemanticarts/ontology-toolkit

tagv1.7.0

Tools to update and export ontology RDF.

created time in 4 days

release semanticarts/ontology-toolkit

v1.7.0

released time in 4 days

PR merged semanticarts/ontology-toolkit

Support --label-language, documentation and test updates.

Made further changes to get WHOI data to render - specifically, had to handle multi-lingual labels on properties and classes, and literals without datatypes, which had to default to xsd:string. After all the change, using this command

onto_tool -k graphic -e https://lod.bco-dmo.org/sparql --data --instance-limit 10000 

produced the attached image. There is quite a bit more to do to improve this - consolidating targets w/ subclasses (such as all the Role sub-classes), hiding some inverses, etc. But the picture does emerge. image

+82 -22

0 comment

7 changed files

bpelakh

pr closed time in 4 days

push eventsemanticarts/ontology-toolkit

Boris Pelakh

commit sha 4705e3895dd38edaf7b504c7ebfb3e295b4ec344

Support --label-language, documentation and test updates.

view details

Boris Pelakh

commit sha 564ed706fd5208649c6b77377b5a4935dd41c8a7

Encode .dot file as utf-8

view details

push time in 4 days

delete branch semanticarts/ontology-toolkit

delete branch : lang-label-support

delete time in 4 days

push eventsemanticarts/ontology-toolkit

Boris Pelakh

commit sha 7680ca214c478ad811c5148834e96aa9c85a72d1

Encode .dot file as utf-8

view details

push time in 4 days

PullRequestReviewEvent

PR opened semanticarts/ontology-toolkit

Reviewers
Support --label-language, documentation and test updates.

Made further changes to get WHOI data to render - specifically, had to handle multi-lingual labels on properties and classes, and literals without datatypes, which had to default to xsd:string. After all the change, using this command

onto_tool -k graphic -e https://lod.bco-dmo.org/sparql --data --instance-limit 10000 

produced the attached image. There is quite a bit more to do to improve this - consolidating targets w/ subclasses (such as all the Role sub-classes), hiding some inverses, etc. But the picture does emerge. image

+81 -21

0 comment

7 changed files

pr created time in 4 days

create barnchsemanticarts/ontology-toolkit

branch : lang-label-support

created branch time in 4 days

issue commentsemanticarts/gist

Circular definition of Task

The problem here is that gist:Task, (as intended by its original author) really does correspond to the event of doing something even if that doing has not happened yet. I have long found that confusing, because the dictionary definition is different.

An important question is whether we genuinely want the concept that is currently modeled, but should call it something besides gist:Task or whether we should change the meaning of gist:Task to align better with common usage of the term. The latter is dangerous.

turingtest37

comment created time in 4 days

issue commentsemanticarts/gist

Circular definition of Task

I disagree - a task is far more specific than a generic event. It's also wrong to say it's been scheduled. And I agree that it's best if the definition doesn't use the same word as the label. Here are some dictionary definitions:

A piece of work to be done or undertaken. A usually assigned piece of work often to be finished within a certain time. A definite piece of work assigned to, falling to, or expect of a person.

I don't love any of these but I'm guessing that between us and them we can come up with good wording.

turingtest37

comment created time in 4 days

issue openedsemanticarts/gist

Circular definition of Task

gist 10.0.0 defines Task as

A task which has been defined and either scheduled or accomplished, or both.

It should read "An Event which has been..."

created time in 4 days