4649Re: [TaxoCoP] Converting Data to SKOS assistance
- Oct 30, 2013I can only speak for my own company's vocabulary management tool--it would be simple to display and edit the additional custom properties if each value was stored as an individual property of the Concept itself, which I believe is what Jim suggested, but you would see the nine annotation values attached to Concept C113266 with no indication that any had been grouped together.A compromise, which would work fine in the TopBraid EVN interface out of the box, would be to declare Annotation as its own concept class (essentially, a subclass of skos:Concept) that had properties like those shown in your annotation table. You could assign a few to Annotation instance 123, and then a Concept could have that Annotation instance as its xyz:annotation value. It would display on the concept data form as a hypertext link that led to the annotation instance.BobOn Wed, Oct 30, 2013 at 4:47 AM, Gabriel Tanase <gabtanase@...> wrote:GabrielThank you,Perhaps this is not possible at all, and - hopefully - perhaps this does not matter for the end-users / downstream systems' perspective.My follow-up question is: since the implementation would be based on customizing the underlying OWL ontology, rather than on plain annotations, how simply would tools that handle annotations out-of-the-box be able to show values from the added property as annotations, or in a manner very similar to how they display annotations?Indeed, that is the intended meaning.IMHO it might have been more obvious if the source database had been normalized e.g. in three tables: Concept(Code, ...) , ConceptAttribute(Code, Name, Value) and ConceptAttributeSource(Code, Name, Value).
Maybe Nathan does not have control over how data is made available in the database.
All they might need is to access the annotative data in a meaningful manner.----------
http://ie.linkedin.com/in/gabrieltanaseOn 29 October 2013 22:14, Bob DuCharme <bducharme@...> wrote:Doing that, you could assign three Q10 values, three Q12 values, and three Q47 values to concept C113266, but I believe he wants to record the fact that first Q10, Q12, and Q47 values go together (as Annotation set 123), the second Q10, Q12, and Q47 values go together (as Annotation set 456), etc., which would require an extra data structure.Bob
- << Previous post in topic Next post in topic >>