Live data from Hacker News

Viewing profile — degyves

degyves

HN member
Joined
Tue, May 06, 2014, 2:39 PM UTC
HN karma
7
Public activity
26 items

About degyves

No profile information was provided.

Recent public activity

  1. comment
    Comment #28865668

    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, RD…

  2. comment
    Comment #25393451

    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 …

  3. comment
    Comment #25389114

    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 …

  4. comment
    Comment #21614983

    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 intelig…

  5. comment
    Comment #21526096

    Some specific reason to not recommend it?

  6. comment
    Comment #20598037

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

  7. comment
    Comment #20140467

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

  8. comment
    Comment #19104387

    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…

  9. comment
    Comment #18889748

    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:…

  10. comment
    Comment #18889679

    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 …

  11. comment
    Comment #18401193

    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 i…

  12. comment
    Comment #18396233

    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, standa…

  13. comment
    Comment #18396168

    Funny that ultra-large-enterprise crap could be applied to Facebook and GraphQL?

  14. comment
    Comment #18396150

    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…

  15. comment
    Comment #18396144

    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 f…

  16. comment
    Comment #18396062

    I think you should read the definition right from the website: https://graphql.org/learn/

  17. comment
    Comment #18396060

    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. comment
    Comment #18396007

    Can you elaborate why SPARQL is the wrong tech?

  19. comment
    Comment #18395999

    From the website: "GraphQL is a query language for your API"

  20. comment
    Comment #18395992

    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 HATEOA…

  21. comment
    Comment #18395980

    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. comment
    Comment #18395561

    Great. Another solution for an already-solved, already-standardized query API language (SPARQL).

  23. comment
    Comment #18034587

    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. story
  25. comment
    Comment #15377537

    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.