I think of the capabilities as akin to the database metadata in JDBC (though metadata is much larger), some people use it some don't but if you don't you do so at your own risk.
I would like to keep it. Claude On Mon, Sep 2, 2013 at 9:31 AM, Chris Dollin <[email protected]>wrote: > On Sunday, September 01, 2013 12:37:02 PM Andy Seaborne wrote: > > It's hard to find many uses in the main code base of capabilities. I > > can only find two uses in main/java at all: > > > > * use of sizeAccurate() in the isomorphism code > > * findSafeContract() in RDF/XML writing. > > Capabilities were added as a way of allowing graphs to describe > how far they went to meet some contracts, eg "you can't update > me, no matter how hard you call add(Triple)". In practice no-one [1] > bothered to query the capabilites before doing something that > they were relevant to ... > > So "experiment that didn't work out" is likely the state of affairs > and dropping capabilities is a good idea ... assuming we can > find suitable replacements around findSafeContract and sizeAccurate > (which might turn out to be documentation that says "don't do that!" > for the iffy cases). > > Chris > > [1] Apart from some of the early Jena developers ... > > -- > RIP Diana Wynne Jones, 1934 - 2011. > > Epimorphics Ltd, http://www.epimorphics.com > Registered address: Court Lodge, 105 High Street, Portishead, Bristol BS20 > 6PT > Epimorphics Ltd. is a limited company registered in England (number > 7016688) > > -- I like: Like Like - The likeliest place on the web<http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
