Text "field" ??

[Don Sheridan]

Hi Tania

 

I am working through some examples prior to the short course next week.

 

Given a graduate profile that has multiple capabilities and a significant amount of explanatory text associated with each capability, is the recommended solution to use the annotations as the location to embed the text?

 

It seems like that was used in bioengineering applications where the entities were alpha-numerics (not self-explanatory)

 

Thanks, Don

 

_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user

[Tania Tudorache]

Hi Don,

Yes, you could use annotation properties to provide the textual description of an entity (e.g., class) in your ontology.

You could use one of the standard annotation properties, rather than making up your own. For example, you could use skos:definition, or the other skos properties.

You can find more information on the different properties that are available in SKOS from here:

https://www.w3.org/TR/skos-primer/

(Sections 2.2 and 2.4)

Tania

---

From: protege-user <[hidden email]> on behalf of Don Sheridan <[hidden email]>
Sent: Thursday, March 23, 2017 8:30:20 PM
To: [hidden email]
Subject: [protege-user] Text "field" ??

 

Hi Tania

 

I am working through some examples prior to the short course next week.

 

Given a graduate profile that has multiple capabilities and a significant amount of explanatory text associated with each capability, is the recommended solution to use the annotations as the location to embed the text?

 

It seems like that was used in bioengineering applications where the entities were alpha-numerics (not self-explanatory)

 

Thanks, Don

 

_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user