4648Re: [TaxoCoP] Converting Data to SKOS assistance
- Oct 30, 2013GabrielThank 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 >>