Closed acoburn closed 5 years ago
👍 except DefaultConstraintService
. I think LdpConstraintService
is more descriptive. The fact that it is on by default isn't as important as the fact that it provides a lot of LDP behavior.
I like your suggestion. I'll update the proposal to use LdpConstraintService
The various no-op service implementations all follow a standard naming convention:
org.trellisldp.<module>.NoopXService
, but the other service implementations really don't.We have some
DefaultXService
classes, and several backend-specific classes (e.g.TriplestoreResourceService
. Those are fine, but others ought to be reviewed.As such, I'd like to propose the following changes:
Other suggestions are welcome.