-
Notifications
You must be signed in to change notification settings - Fork 35
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
Pair Credential with their Supporting documents #357
Comments
@BenjaminMoe , great that you've moved this conversation to a dedicated issue. @OR13 , ref the discussion on the initial PR, I understand that we can add pictures on the .yml files. But I don't think we should. |
@nissimsan do you agree to abide by OAS 3 and treat descriptions as markdown? or are you saying we should profile down from OAS 3 and forbid markdown in descriptions? |
@OR13, I would love support for markdown OAS! But it's a different point I am trying to make. @BenjaminMoe has externalized references to pictures like the one below into a separate file. And I think that's correct; while useful to display such legacy pictures on our main page, I wouldn't want to include them as part of the formal schema. |
The formal schema could include "based on" or "derived from" or "influenced by" or similar links to the scanned paper forms. I wouldn't include the actual images in the formal schema. |
https://swagger.io/specification/
|
+1 |
descriptions.json
into schema description
Changed the title as my updated PR document use the same json work around, in favor of moving supporting docs to their own section. https://github.com/w3c-ccg/traceability-vocab/pull/364/files |
Use openAPI 3.0 specification for markdown fields. |
I am a +1 for using absolute URLs and markdown. |
Needed improvement. |
@BenjaminMoe any updates on this? |
Related to #352. Reference images for documents have been included in
descriptions.json
file. This is a stop-gap for re-organizing the documentation. The reference images for specific document should be moved to their respectiveyml
files in a future PR.The text was updated successfully, but these errors were encountered: