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

Should we add a URI/links field to the schema? #1

Open
hainesr opened this issue Apr 20, 2024 · 3 comments
Open

Should we add a URI/links field to the schema? #1

hainesr opened this issue Apr 20, 2024 · 3 comments
Labels
question Further information is requested

Comments

@hainesr
Copy link
Member

hainesr commented Apr 20, 2024

I forgot to ask about this in the room, sorry.

I wonder if we should add a field to store a link (or links) out to further information and references. For example, with the SWEBOK terms we could link out to the sections of the online SWEBOK book we found. If we allowed this field to be an array, then we could reference multiple sources, if appropriate.

Thoughts?

@hainesr hainesr added the question Further information is requested label Apr 20, 2024
@bernhold
Copy link
Contributor

I've added a references array that we can do whatever we want with. Though for SWEBOK in particular, I was planning to key on the SWEBOK section number (perhaps with some help from a data file, depending on what the links need to look like).

@bernhold
Copy link
Contributor

Also, @hainesr , didn't you find a markdown source for the SWEBOK somewhere? Or was that a red herring?

@hainesr
Copy link
Member Author

hainesr commented Apr 29, 2024

Hi @bernhold, I found this: https://github.com/ligurio/swebok-v3

It looks like it's OK, but I'm not familiar enough with the material to know for sure. And I'm not entirely convinced of its legitimacy, if you know what I mean...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants