On 21/11/2019 18:30, ajs6f wrote:
I would like to look at the fairly large number of methods on classes like Resource and
Model and see if we can corral and regularize them a bit. I'm not against functionality,
of course, but we've built up those APIs via the "coral reef" model
(accumulation) and so we have little oddities like:
Statement getProperty(Resource s, Property p, String lang)
and
Property getProperty(String nameSpace, String localName)
but
Statement getRequiredProperty(Resource s, Property p)
with no
Property getRequiredProperty(String s, String p)
I don't disagree with the general point but this specific example
doesn't resonate with me. The latter doesn't exist because it would make
no sense.
I suspect the underlying point is that the second form of getProperty is
badly named and in retrospect perhaps could have been called makeProperty.
Dave
