degyves · HackerTrans

5 ปีที่แล้วdiscuss

In fact you can use XML, but not barebones XML. XML does not contain semantics, which is needed to achieve interoperability. So you should use some more specialized XML, namely, RDF/XML. Which of course will increase complexity to XML. You can use also JSON-LD, which is a more complex JSON bc it adds semantics.

degyves

6 ปีที่แล้วdiscuss

Growing anywhere is not enough reason to use something. A lot of things are available anywhere but not all of these will be safe for your community. Sacred plants are more complex than the individual impact. It has consequences on your society and this is why its management is by law restricted to native nations.

degyves

6 ปีที่แล้วdiscuss

I'm native indigenous from Oaxaca, Mexico, home of several sacred ceremonies with magic mushrooms and other plants from millennia. I'd like to share that our Native Nations do not give permission for scientific research of magic mushrooms outside our culture. This is not an egoistic stand, but it is for your own safety. Sacred plants on pharma and marketing industries hands will only create more damage than good. If you are interested to learn about sacred plants you must learn respect from native nations and come, live here and share for a time, then a request to research can be asked to the community.

degyves

7 ปีที่แล้วdiscuss

That depends of which precise definition of consciouness you're talking about, which is a flame wars research field. But it is a consensus that consciouness is not equal to inteligence.

degyves

7 ปีที่แล้วdiscuss

Some specific reason to not recommend it?

degyves

7 ปีที่แล้วdiscuss

How "most advanced graph database" does not supports already standardized SPARQL query? Have you found anything wrong with standard SPARQL?

degyves

7 ปีที่แล้วdiscuss

The most impressive to me, is to read only a single comment worried about the ecological impact and the sustainability

degyves

7 ปีที่แล้วdiscuss

Just start with Apache Jena, standards based with RDF as the exchange format and SPARQL for the query language. Others solutions may use proprietary stuff for better vendor lock-in: This is completely up to you if you want that. But with Apache Jena you can change later to other KG databases. Also: Apache Jena is easy to work with, since it includes Fuseki to start directly using it as a web API.

https://jena.apache.org/ https://jena.apache.org/documentation/fuseki2/

Once you need "big data" for your personal Knowledge Graph, you can use other RDF stores, without vendor lock-in.

degyves

8 ปีที่แล้วdiscuss

Even more, we're already there: US ONC Health IT and HL7 are currently on the FHIR standard, which is slowly integrating linked data principles. E.g. currently uses JSON-LD: https://www.healthit.gov/buzz-blog/interoperability/heat-wav...

degyves

8 ปีที่แล้วdiscuss

Not only now Linked Data + RDF is even simpler and nicer to learn: There are currently more libraries to work with. Also it is more critical than ever for many industries.

Current solution for several issues related with electronic health records concluded to create the new standard, to use RDF and linked data, which solved most of the issues on the previous standard. See FHIR: https://en.wikipedia.org/wiki/Fast_Healthcare_Interoperabili...

In fact, current linked data discussions seem to me that become relevant again because it is more clear now that we have been misusing/overusing/ bad REST, microservices architectures and GraphQL for some already analyzed and solved problems.

But, of course, for a single application which doesn't require interoperability, not requiring standardized data exchange formats, not requiring support for flexible data representation, Linked Data and RDF will be clearly unnecessary. But on time, the future of data interconnection plays on the side of Linked Data IMHO.

Until now, current attempts to create some Linked Data + RDF alternate infraestructures are more likely to create ad-hoc, informally specified, bug-ridden, slow implementations of Linked Data and RDF.

comments