No untyped individuals about i40kg HOT 21 CLOSED

Individuals of this kind have been removed. Please have a look and we can close the issue.

from i40kg.

No, we can´t see the image for yourself how many untyped individuals are.

from i40kg.

Please have a look at this. Let me know if this is not the way. Places and Country

from i40kg.

I need to understand sto:hasClassification and sto:StandardClassification to deal with some of these instances. What is the source of this information? I am a little hesitant to work on things that I don't understand well since I am not the original author of these things.

from i40kg.

The way you did it with Places and Countries is the right way.
Please have a look at this example regarding sto:hasClassification and let me know if you understand this.

from i40kg.

Please have a look at this commit. Use protégé and texteditors at the same time.

from i40kg.

I understand the relationships and instance examples but I don't have necessary information to define these instances. For example. What is CommunicationSubModel . I tried to look at related content in the file but I don't know how to classify it.

from i40kg.

I am using protégé and sublime text editor parallely.

from i40kg.

Very valid question. Please have a look at this document on page 19. Second, this the rami:CommunicationSubModel belongs to the rami ontology, thus it should be type of some of the rami classes.

from i40kg.

What is sto:Concern. Source Please

from i40kg.

Also why are we redefining sto:Configuration and using rami:Configuration. Its a source of confusion I think. Better to maintain one consistently.

from i40kg.

Yes, this is a mistake, there should only exist rami:Configuration.

from i40kg.

So, same applies to sto:Communication, sto:ConditionMonitoring ?

from i40kg.

Please, when you do a link, press the key Y, otherwise, the link is lost.

from i40kg.

I understand the problem but did not understand when to press the Y.

from i40kg.

When you link to the code in Github, e.g., as in sto:Communication above. It creates a unique link.

from i40kg.

Like here sto:Communication.

from i40kg.

sto:Communication. I have tried to do the same but I think the link does not work if there are modifications done to the file.

from i40kg.

Now it is correct. It does not matter if there are modifications. Well, in this case, sto:Communication is an instance of rami:AdministrationShellSubModel, so yes, it should be renamed to rami:Communication.

from i40kg.

These few individuals are still without class. Please have a look to close this issue.

from i40kg.

All of the individuals are looked into and sorted.

from i40kg.