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

Add support for relative paths? #2

Open
lurnid opened this issue Jul 1, 2022 · 0 comments
Open

Add support for relative paths? #2

lurnid opened this issue Jul 1, 2022 · 0 comments

Comments

@lurnid
Copy link
Member

lurnid commented Jul 1, 2022

The specs state that:

Where a field requires a link to an external resource or path, absolute or relative paths may be used.

Relative paths shall be relative to the location of the Open Know-How Manifest in the documentation repository. 

Absolute paths shall include the full path to the resource including the protocol. 

Paths shall use forward slashes.

Is it possible to add validation for relative paths in the validator? The specs state that "Relative paths shall be relative to the location of the Open Know-How Manifest in the documentation repository.". This assumes that the file is accessed by a crawler. If the manifest is to be used as a basis for portability then someone should be able to use the manifest as a stand-alone file to retrieve all of the project's files. As such, relative paths are not useful in this context so the validator does not currently check for them, only absolute URI's. Is it possible to incorporate the use of relative paths?

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

No branches or pull requests

1 participant