Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

change gist:Specification textual description #431

Closed
marksem opened this issue Feb 15, 2021 · 5 comments · Fixed by #991
Closed

change gist:Specification textual description #431

marksem opened this issue Feb 15, 2021 · 5 comments · Fixed by #991

Comments

@marksem
Copy link
Collaborator

marksem commented Feb 15, 2021

Proposal: change gist:Specification textual description to say "A requirement or set of requirements to be satisfied by a material, design, product, or service."

Rationale:

Currently (through v9.5.0), gist:Specification is a subClassOf gist:Requriement. But its textual definition is: "A set of requirements to be satisfied by a material, design, product, or service." As such, it would most naturally seem to be a sub of Collection.

If we change to say it is "a requirement or set of requirements," we could be OK since Requirement and Collection are not disjoint. This allows us to keep our textual definition part about "… to be satisfied by a material, design, product, or service", which I like because it distinguishes it from a more general Requirement.

(@mkumba supports this change)

@rjyounes
Copy link
Collaborator

To be legalistic, a set may have one member. Or none - perhaps we should say "...a non-empty set of requirements..."

That being said, the proposal seems fine to me given ordinary English usage.

@uscholdm
Copy link
Contributor

Or getting rid of the geek-speak altogether: One or more requirements. Simpler, if a tad less precise.

@rjyounes
Copy link
Collaborator

This is subsumed by #534 but I'm leaving it open so we make sure to consider the specific issues addressed here.

@uscholdm
Copy link
Contributor

SUGGESTION: change the definition to be:

  • "One or more requirements to be satisfied by a material, design, product, or service."

@rjyounes
Copy link
Collaborator

I agree with @uscholdm's suggestion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants