Re: [protege-user] hello
Michael DeBellis <[email protected]>
| Newsgroups | gmane.comp.misc.ontology.protege.owl |
|---|---|
| Message-ID | <CALGFikd+uRitndBE91LZ3EZnK44nX_mUd-sVepnoEmYRoeeSuA@mail.gmail.com> |
Just realized I didn't answer your second question: also in the turtle rendering tab why it shows me the full IRIs from all > entities and not with the prefix? Not sure what you mean by the "turtle rendering tab". I don't see that tab in the tabs under Window>Tabs Do you mean just the ttl file that gets generated when you save the ontology in Turtle format? I just checked and it does indeed use the full IRIs. Not sure why. My guess is it may be a bit more efficient and since most people seldom edit those ttl files directly having the full IRIs doesn't really matter. The only time (unless you are one of those developers who still thinks "real programmers use vi") you should directly edit those files is when you have some unexplained behavior because some weird character or something krept into your file. If you have a Turtle Rendering Tab in Protege my guess is you are using some plugin that I'm not aware of that creates such a tab. If that's the case please let us know. Michael On Thu, Jan 23, 2025 at 6:14 AM stathoula terzidou <[email protected]> wrote: > i try to add a prefix from the 'Ontology Prefixes' tab and clicking the + > button. At first seems to create it but when switching tabs it disappears > i have a class Course and want to use the schema.org/Course so i was > thinking to create a prefix sch: <http://www.schema.org/> and make the > class Course a owl:Class, sch:Course . > is this correct? > also in the turtle rendering tab why it shows me the full IRIs from all > entities and not with the prefix? > _______________________________________________ > protege-user mailing list > [email protected] > https://mailman.stanford.edu/mailman/listinfo/protege-user > _______________________________________________ protege-user mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/protege-user