Full URL or prefixed shorthand for predicates?

[despens]

The extension is outputting URIs verbatim as set up in the UI, right? So if I type owl:sameAs that'll go into the RDF, if type http://www.w3.org/2002/07/owl# sameAs that will go there?

I think that would be good since it gives curators the power to set up prefixes in their triple store or elsewhere if they need to, otherwise the full URIs would be used.

[JeroenDeDauw]

Please note there already is some discussion about what should be allowed for objects: #20 (comment)

@despens are you also talking about objects? The input of predicates is limited by the values in the dropdown.

[paulduchesne]

Just following up the question around prefixed entities for objects, as discussed in #20 I believe these will need to be full URLs. Currently testing the extension, if a prefixed entity is added as mapping it will injected into the turtle outpoint verbatim which will ultimately confuse the triplestore as there is no opportunity to clarify what the prefix refers to.

Going in this direction also allows for validation as to whether the submitted object is a URL.

[malberts]

Are there any requirements for how strict the URL validation needs to be? Should this match what is allowed in the normal Wikibase URL field or should it be more restrictive?

This will be pattern-based validation only, so it won't include checking if the URL actually exists.

[paulduchesne]

Understood, I think standard URL restriction should be sufficient.