okh:repo - Web-View or git (clone) URL?

[hoijui]

This is a question I have come about a LOT of times in other places already. In practice, both makes sense, and while in the case of github.com and gitlab.com, it is possible to derive one from the other, that is not generally the case. So the question is, should we have both (one property each?), or should we stick to one of the two (git clone URL, which protocol to be preferred?)

example Web:

repo: "https://github.com/OPEN-NEXT/LOSH/"

This can be put into the browser to see the repo.

example clone:

repo: "https://github.com/OPEN-NEXT/LOSH.git"

This can be used as git clone https://github.com/OPEN-NEXT/LOSH.git.

... as said, these two are very similar in this case, and one can derive one from the other, but that might not always be the case, an done also needs to first detect which one it is, and then possibly generate the other form, depending on which one needs.

[moedn]

not quite sure, what the question is, but maybe @ahane has an opinion on that

[hoijui]

I extended the description above.

[moedn]

hmm, at the moment I'd leave things as they are:

• I assume people would want to check the repo first before they clone it
• we use the repo URL for global identification; of course the git clone URL would also work, but I feel the bare repo URL is the better match

or am I missing something?

[hoijui]

As I see it now, we should accept all the repos in the manifest, and then provide always the same (e.g. the web-view one) in the RDF, or even supply all the URLs:

• Web-view
• git clone URL
• ssh clone URL
• http(s) clone URL
• prefix for files (with version/branch variable)
• prefix for dirs (with version/branch variable)
• prefix for raw (with version/branch variable)

[hoijui]

If we make our projects/Modules owl:subClassOf doap:Project, we can use doap:repository and doap:GitRepository (or other sub-classes of doap:Repository), which in turn have linked to them one or more forms of the URLs mentioned in this issue.

see doap