degyves

9 ms·

1.
by degyves 5y ago
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.
2.
by degyves 6y ago
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 soci
3.
by degyves 6y ago
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 m
4.
by degyves 7y ago
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.
5.
by degyves 7y ago
Some specific reason to not recommend it?
6.
by degyves 7y ago
How "most advanced graph database" does not supports already standardized SPARQL query? Have you found anything wrong with standard SPARQL?
7.
by degyves 7y ago
The most impressive to me, is to read only a single comment worried about the ecological impact and the sustainability
8.
by degyves 8y ago
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 Ap
9.
by degyves 8y ago
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/inter
10.
by degyves 8y ago
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 r
11.
by degyves 8y ago
SPARQL results DO have an inherent structure. Even more, this is why projects like Eclipse Lyo can automatically convert SPARQL results directly to Java Objects. So no, SPARQL it is not intended to be used directly but as a product for a li
12.
by degyves 8y ago
Yeah, if you are writing HATEOAS APIs just by personal preference then you are using the wrong technology. You should write HATEOAS to make sure your API will be consistent, standard and automatically browsable on the long term.
13.
by degyves 8y ago
Funny that ultra-large-enterprise crap could be applied to Facebook and GraphQL?
14.
by degyves 8y ago
Oh yeah, GraphQL is backed by Facebook (may that be a hint of its momentum, like its support for React?) , unlike SPARQL which is a _standard_. You can also convert from PostgreSQL, MySQL, DB/2 and others to SPARQL. Still, only differe
15.
by degyves 8y ago
I think you should read it directly from the website: "GraphQL is a query language for your API, and a server-side runtime for executing queries by using a type system you define for your data." You need a type system to bypass th
16.
by degyves 8y ago
I think you should read the definition right from the website: https://graphql.org/learn/
17.
by degyves 8y ago
I think GraphQL is just an way to bully the efforts of the W3C to standardize web technologies. It not just is non-standard, also is breaks any advantage of the HATEOAS principle.
18.
by degyves 8y ago
Can you elaborate why SPARQL is the wrong tech?
19.
by degyves 8y ago
From the website: "GraphQL is a query language for your API"
20.
by degyves 8y ago
Maybe because it IS a query language? From the website: "GraphQL is a query language for your API"... just that it is _not_ a standardized API, so we won't take advantage of HATEOAS.
21.
by degyves 8y ago
GraphQL also demands a certain data model. Just that it is not standardized. And no, RDF/XML is not the only representation for SPARQL. It can deal also with JSON.
22.
by degyves 8y ago
Great. Another solution for an already-solved, already-standardized query API language (SPARQL).
23.
by degyves 8y ago
We actually are on the semantic web for healthcare. See: http://wiki.hl7.org/index.php?title=RDF_for_Semantic_Interop... Other fields are moving towards semantic also
24.
by degyves 9y ago
That's when having mongodb+RDBMS with the added complexity is really justified. On common cases, just drop mongodb and use the RDBMS for everything.
25.
How to correctly ask for feedback on your dev team(linkedin.com)
2 points by degyves 9y ago|0 comments