Some good advice

I want the SDshare specification work here  to get off to a good start, but I'm already worried on the amount of focus there is here on how SDshare will be physically implemented by the triplestores. We have at least three companies in the community that  have stated that they already have or intend implement SDshare in their triplestore. I have seen other standardization work being severely disrupted or even cancelled by strong personalities from different implementers, where they intentionally try to keep the standard close to how they themselves have implemented it rather than trying to find work for the best solution in general. I'm not saying this will happened here, but in general focusing on implementation issues in in our situation is in my experience a very bad idea. The only way I know to avoid this is to decide from the beginning of the specification work to strictly take an academic approach and disregard implementation issues - programmers are usually smart people and they will figure it out somehow.

--
Kind regards,
Inge Henriksen.

Meronymy
Forskningsparken, Gaustadalléen 21, 0349 Oslo, Norway.
Phone: +47 40 45 44 74
E-mail: inge@meronymy.com<mailto:inge@meronymy.com>
Web: www.meronymy.com<http://www.meronymy.com/>
Twitter: @MeronymyCorp<http://twitter.com/MeronymyCorp> & @ihenriksen<http://twitter.com/ihenriksen>
LinkedIn: http://no.linkedin.com/pub/inge-henriksen/1/b50/4b6
About me: http://about.me/ingehenriksen

[logo]