I am considering storing the contents of a web application in an RDF or OWL ontology instead of RDBMS.
However, when I research ontologies, they seem to always exist in the context of publicly accessible data warehouses that serve as the basis of the semantic network. I have never heard that they are used as a mechanism for the content of a web application.
Is it wise to use an ontology instead of RDBMS for such an application?
(Again, this is only for content. User data, commerce and the like will remain in the database, as I do not see the need to reinvent the wheel there.)
" - RDF OWL", " XML "?
, , . . . - . .
, , ? , , . , , - , . , , , concurrency, ACID . , , , ." XML ", , . , XML- , , .
RDBMS? , SQL. , , " ", SQL . SQL . . , SQL ( ), SQL , .
, . . RDF , , , Triplestore.
,
Source: https://habr.com/ru/post/1739367/More articles:JSONP Long polling always loading - cometLinq to Entities Convert DateTime - datetimesvcutil, WSDL, and the created interfaces are not sufficient for implementation - wsdlA jsonp comet hanging request causes an ugly “download” state in browsers - javascriptUIWebView NSURLRequestReloadIgnoringLocalCacheData does not actually ignore the cache - cachingКак добавить дополнительный маршрут? - c#Why are views loaded from nibs placed 20 pixels down from the status bar? - iphoneAvoid loading unnecessary data from db into objects (web pages) - oop.NET: What is the purpose of the ProhibitDtd property in XmlReaderSettings? Why is DTD a security issue? - .netHow to name 2 methods with the same signatures - c #All Articles