handle obsolete properties in BioPortal #93
Comments
galviset
referenced
this issue
in EarthPortal/ontologies_linked_data
Mar 14, 2024
Feature: Add request all languages unit test
galviset
referenced
this issue
in EarthPortal/ontologies_linked_data
Mar 14, 2024
…n (#96) * fix json serializer nil exception (#79) if hash was missing @context key the json serializer throwed a nil exception * Merge pull request #87 from ontoportal-lirmm/fix/achived-submission-space-optimization Fix: Archived submission space optimization * Merge pull request #71 from ontoportal-lirmm/feature/support-multilingual-read-one-language-from-request-parameter Feature: Support multilingual - Add read one language from request parameter tests * Merge pull request #73 from ontoportal-lirmm/feature/add-request-language-to-context Feature/add request language to context * fix json serializer nil exception (#79) if hash was missing @context key the json serializer throwed a nil exception * Merge pull request #83 from ontoportal-lirmm/feature/add-request-language-to-context Feature: add request language to context follow up * Merge pull request #93 from ontoportal-lirmm/support-multi-lang-part-02 Feature: Add request all languages unit test * Merge pull request #94 from ontoportal-lirmm/feature/support-multi-langual-search Feature: Support multilangual search --------- Co-authored-by: Raimi Solorzano Niederhausen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
An obsolete property can be declared in the same was as an obsolete class, by annotating the property with owl:deprecated set to "true".
BioPortal doesn't handle these obsolete properties in any way. Implement handling of obsolete properties parallel to our handling of obsolete classes (e.g., include the same options in the new submissions UI).
The text was updated successfully, but these errors were encountered: