Re: "Microsoft Access" for RDF?

On 19 Feb 2015 21:42, "Kingsley Idehen" <kidehen@openlinksw.com> wrote:

>> No, this is dangerous and is hiding the truth.
> What?

(Just to clarify my view, obviously you know this :) )

That RDF Triples are not ordered in an RDF Graph. They might be ordered in
something else, but that is not part of the RDF graph. (Reification
statements can easily also become "something else")

So if you tell the user his information is just RDF, but neglect to mention
"and then some", he could wrongfully think that his list of say "preferred
president" has its order preserved in any exposed RDF.

If you don't tell him it is RDF (this is now the trend of Linked Data
movement..), fine! It's just a technology - he doesn't need to know.


> You can describe collections using RDF statements, I don't have any idea
how what I am talking about implies collection exclusion.

My apologies, I got the impression there was a suggestion to control
ordering of triples without making any collection statements.


>> Don't let the user encode information he considers important in a way
that is not preserved semantically.
> ??

I simply meant to not store such information out of band, e.g. by virtue of
triple order or comments in a Turtle file, or by "magic" extra bits in some
database that don't transfer along to other consumers of the produced RDF.

It should be fine to store "view"-metadata out of bands (e.g. which field
was last updated) - but if it has a conceptual meaning to the user I think
it should also have meaning in the RDF and the vocabularies used.

If you are able to transparently do the "right thing" semantically, then
hurray!


> Why do you think we've built an RDF editor without factoring in OWL?

Many people are still allergic to OWL :-(

And also I am still eager to actually see what you are talking about rather
than guessing! :-)


> I think we are better off waiting until we release our RDF Editor. We
actually built this on the request of a vary large customer. This isn't a
speculative endeavor. It's actually being used by said organization as I
type....

Looking forward to have a go. Great that you will open source it!