If you could hover over that "this claim has a description or image" icon and get a description that pops out via Javascript, I would read them more often
Yes, the explanation shouldn't alter the original claim, but it can certainly clarify it - why offer a description at all, otherwise? Some concepts are just too complex or ambiguous without further qualification. Surely as a law student, you of all people would concede that, Kara?
There's a number of reasons to offer a description. Support and commentary are the only one's I can really get behind, though. If the description alters the meaning of the claim enough, the claim is badly worded.
I hear where you’re coming from D’A and I agree that the more a claim can stand on its own the better, but I find myself siding with Prunella’s and Rachel’s comments.
Discussion (7)
It's to be expected, so I'm not bothered
If you could hover over that "this claim has a description or image" icon and get a description that pops out via Javascript, I would read them more often
Claims inspired by this comment
Jyte should enable ‘next’ and ‘previous’ browsing of claims from within claim pagesThe explanation shouldn't alter the original claim, so I don't mind.
Yes, the explanation shouldn't alter the original claim, but it can certainly clarify it - why offer a description at all, otherwise? Some concepts are just too complex or ambiguous without further qualification. Surely as a law student, you of all people would concede that, Kara?
I am reminded that claims should stand on their own.
D'A
There's a number of reasons to offer a description. Support and commentary are the only one's I can really get behind, though. If the description alters the meaning of the claim enough, the claim is badly worded.
D'A
Bugger. s/one's/ones/
D'A
I hear where you’re coming from D’A and I agree that the more a claim can stand on its own the better, but I find myself siding with Prunella’s and Rachel’s comments.