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
@grahamtriggs points out that prefixes for Java are now "handled" as a result of VIVO-1408 and then a workaround was provided for jenatools in the form of VIVO-1408
This issue would implement prefixes as transparent simple text substitutions. No '#' in a java class path interpreted by software in some special way. Prefixes for java class paths should end in '.' so that one can write prefix:path.path and the substitution occurs in a transparent way, leading to syntactically correct path.
Requires discussion.
The text was updated successfully, but these errors were encountered:
Based on Jim Blake's comment in VIVO-1408, it appears that a namespace can not be terminated with a ".":
It would be much easier to read these strings if we could use RDF namespaces with corresponding prefixes. However, the period is not a valid delimiter for a namespace.
I guess as see the prefixes as a shortcut and the string following the prefix as the text to substituted for the prefix. The notion that the user's content must be manipulated is a concern.
Mike Conlon (Migrated from VIVO-1519) said:
@grahamtriggs points out that prefixes for Java are now "handled" as a result of VIVO-1408 and then a workaround was provided for jenatools in the form of VIVO-1408
This issue would implement prefixes as transparent simple text substitutions. No '#' in a java class path interpreted by software in some special way. Prefixes for java class paths should end in '.' so that one can write prefix:path.path and the substitution occurs in a transparent way, leading to syntactically correct path.
Requires discussion.
The text was updated successfully, but these errors were encountered: