twosixlabs / icas-ontology Goto Github PK

Both host:existsAs and hardware:hasFormFactor have host:Host in rdfs:domain and hardware:ComputingMachine in rdfs:range. They also both refer to each other with an owl:inverseOf .

I'm guessing one of them should have the rdfs:domain and rdfs:range reversed, and I can make a pull request. But I'm not sure which.

I had a conversation with Dan Olsher at DO about generating keywords for elements of the ontology, and noted that we had already explored doing that, with mixed results. A sampling of some of the keywords we were able to generate for datatype properties is included below. We determined that this was not effective enough without massive manual curation to include directly into the ontology.

{
    "http://www.invincea.com/ontologies/icas/1.0/acl#hasOrder": [
        "control",
        "within",
        "postion",
        "list",
        "number",
        "access",
        "position",
        "entry",
        "order"
    ],
    "http://www.invincea.com/ontologies/icas/1.0/acl#isRecursive": [
        "recursive",
        "grant",
        "recursion",
        "recursively",
        "object",
        "iterative",
        "acl",
        "objects",
        "listed",
        "child",
        "entries",
        "permissions"
    ],
    "http://www.invincea.com/ontologies/icas/1.0/authentication#authStatus": [
        "status",
        "success",
        "etc",
        "could",
        "auth",
        "failure",
        "authentication",
        "inprogress",
        "event"
    ],
    "http://www.invincea.com/ontologies/icas/1.0/authentication#loginName": [
        "account",
        "via",
        "name",
        "specific",
        "used",
        "identify",
        "keyboard",
        "input",
        "login",
        "string"
    ]
}

The License mentioned in the README is MIT.
For machine readability though, it should be in its own file. Then GitHub would also show it, for example.

Great to finally see this body of work!

The GitHub Page states that distribution is only through an NDA with DARPA ICAS Program.

Distribution

This ontology is subject to public release approval by DARPA and as such may not be distributed outside of the DARPA ICAS program except under the terms of a non-disclosure agreement.

Can we get clarification/updates on licensing/distribution/use made to the GitHub Repo

Do I have to use rdfs:label for pointing hostname to qualify an A record?

Usually in DNS A records, we can find something like :
text.esams.wikimedia.org. IN A 91.198.174.232

Is the following the right way to represent it?

     <http://wikimedia.org/address1> a ipnet:Address;

                                     ipnet:hasAddressValue '91.198.174.232'.

    <http://wikimedia.org/a_record1> a dns:A;

                                    dns:resolvesToAddress <http://wikimedia.org/address1>;

                                    rdfs:label 'text.esams.wikimedia.org.'.

Or is there a better way to do this?

In https://github.com/twosixlabs/icas-ontology/blob/master/ontology/hardware.ttl, is :Ether801_11 supposed to mean "wi-fi" interface? Isn't the standard 802.11 though (not 801.11)?
https://en.wikipedia.org/wiki/IEEE_802.11

I have noticed some properties in the filesystem ontology akin to this:

:lastAccessedOn
    a owl:DatatypeProperty, owl:FunctionalProperty ;
    rdfs:domain :Directory, :File ;
    rdfs:range xsd:dateTimeStamp .

As is it currently written, this implies that the domain of :lastAccessedOn is the intersection of classes :Directory and :File, not their union.

Per the RDF Schema 1.1:

Where a property P has more than one rdfs:domain property, then the resources denoted by subjects of triples with predicate P are instances of all the classes stated by the rdfs:domain properties.
Any entity that has this property is simultaneously a file and a directory.

The solution would be to specify a class that both :File and :Directory are subclasses of. I think it would be best to add some overarching class like :FileSystemEntry and use that, since even volumes, links etc. might have these attributes.

In processing the Turtle-formatted files in this project with Jena, I found about two dozen that would not parse due to the presence of a property "dc:creator:". The second colon is the cause of the issue.

The files:

authentication.ttl: dc:creator: "Invincea Labs"@en ;
capec.ttl: dc:creator: "Invincea Labs"@en ;
controls.ttl: dc:creator: "Invincea Labs"@en ;
cwe.ttl: dc:creator: "Invincea Labs"@en ;
dhcp.ttl: dc:creator: "Invincea Labs"@en ;
dns.ttl: dc:creator: "Invincea Labs"@en ;
email.ttl: dc:creator: "Invincea Labs"@en ;
filesystem.ttl: dc:creator: "Invincea Labs"@en ;
filesystemartifacts.ttl: dc:creator: "Invincea Labs"@en ;
hardware.ttl: dc:creator: "Invincea Labs"@en ;
host.ttl: dc:creator: "Invincea Labs"@en ;
indicators.ttl: dc:creator: "Invincea Labs"@en ;
log.ttl: dc:creator: "Invincea Labs"@en ;
maec.ttl: dc:creator: "Invincea Labs"@en ;
memory.ttl: dc:creator: "Invincea Labs"@en ;
memoryartifacts.ttl: dc:creator: "Invincea Labs"@en ;
metadata.ttl: dc:creator: "Invincea Labs"@en ;
mime.ttl: dc:creator: "Invincea Labs"@en ;
nic.ttl: dc:creator: "Invincea Labs"@en ;
osplatform.ttl: dc:creator: "Invincea Labs"@en ;
oui.ttl: dc:creator: "Invincea Labs"@en ;
privilege.ttl: dc:creator: "Invincea Labs"@en ;
process.ttl: dc:creator: "Invincea Labs"@en ;
registry.ttl: dc:creator: "Invincea Labs"@en ;
tapio.ttl: dc:creator: "Invincea Labs"@en ;
uri.ttl: dc:creator: "Invincea Labs"@en ;
user.ttl: dc:creator: "Invincea Labs"@en ;