Difference between revisions of "Graph Terminology/Options"

From RDF Working Group Wiki
Jump to: navigation, search
(Created page with "== Option 1 (baseline) == (this was the agreement the last time this was brought to a decision; things seem to have changed enough in the model since then for the decision to no…")
(No difference)

Revision as of 11:02, 24 August 2012

Option 1 (baseline)

(this was the agreement the last time this was brought to a decision; things seem to have changed enough in the model since then for the decision to no longer be binding.)

g-snap
RDF Graph
g-box
Graph Container

Option 2

g-snap
RDF Graph
g-box
RDF data source

Option 3 (retronym)

g-snap
abstract graph, abstract RDF graph
g-box
[something] graph, [something] RDF graph.

... where [something] hasn't quite been determined yet. Options include:

  • maintained (but what if it's been abandoned?)
  • mutable (but what if it's a frozen snapshot?)
  • named (but wont that really confuse people?)
  • stored (but what if it's dynamically generated?)
  • available (but what if it's access controlled?)
  • concrete (awkward word)
  • real
  • nonabstract
  • located
  • distinct
  • ...

The idea here is that when people say "graph" or "RDF graph" these days, they often mean g-box. So we could go with the flow here, let them do that, and just come up with adjectives people can use to distinguish between g-snaps and g-boxes when necessary. What kind of graph is a g-box?