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

Artifact Design, Artifact Model, and Artifact Function Specification #444

Open
avsculley opened this issue Aug 22, 2024 · 0 comments
Open
Assignees
Labels
for 2.0 release This label indicates updates to be made in the 2.0 release, which will include a new IRI format.

Comments

@avsculley
Copy link
Contributor

  1. Should 'Artifact Model' be a subclass of 'Artifact Design'? It is currently, but I don't think so, as artifact designs prescribe objects and artifact models prescribe functions and qualities. This separation of prescriptions of objects and prescriptions of the SDCs those objects have is recognized already by the location of 'Artifact Function Specification' in the hierarchy.

  2. 'Artifact Function Specification' also seems to overlap somewhat with the meaning of 'Artifact Model.' So, I'm not sure that both classes are needed in their current form.

  3. That said, even if I'm wrong, the definition of 'Artifact Model' should be changed to reflect the fact that its parent class is 'Artifact Design.'

@neilotte neilotte added the for 2.0 release This label indicates updates to be made in the 2.0 release, which will include a new IRI format. label Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for 2.0 release This label indicates updates to be made in the 2.0 release, which will include a new IRI format.
Projects
None yet
Development

No branches or pull requests

3 participants