You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
The specs state that:
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?
The text was updated successfully, but these errors were encountered: