• Facets (new session)
• Description
• Metadata
• Settings
  • Rule: ActivityStreamsMapasEquivalentb3sb3sifpfacetshttp://www.w3.org/2002/07/owl#ldpoffers ontologyoplwebrel-me-authschema-oloskos-transurn:det:rdf:labelurn:rdfs:subclass:subproperty:inference:rulesvirtrdf-eturtle-containersvirtrdf-hashtagvirtrdf-ifpvirtrdf-labelvirtrdf-meta-entity-classvirtrdf-urlNone
    
  • Inverse Functional Properties: Disabled (fastest) Apply to subjects only Apply to objects only Apply to both subjects and objects
  • "Same As": Disabled (fastest) Apply to subjects only Apply to objects only Apply to both subjects and objects (recommended) Apply to subjects, objects and predicates (not recommended on big datasets) Apply to predicates only (special use cases only)

About: Why both the Graph and Relational Database Monikers are problematic     Goto   Sponge   NotDistinct   Permalink

An Entity of Type : schema:BlogPosting, within Data Space : www.openlinksw.com associated with source document(s)

Type: CreativeWorkBlogPosting New Facet based on Instances of this Class

A blog post expanding on why Graph and Relational Database Monikers are problematic. Graph Data is like saying “Data Data”. Thus, a Graph Database is like saying “Data Data Document”. That phrase sounds nice to the ear, and the visualization are temporarily appealing, but ultimately a path to confusion.