URLs and hyperlinks within text, within a concept description

[rowan.brownlee]

Hi,

A question about URLs and hyperlinks within text, within a concept description.  

As part of a description of a concept, they wish to refer to a related resource.  They understand that they may include a link such as rdf:seeAlso, or a link from another ontology expressive of the particular type of relationship.  But they also wish to include a URL within a text narrative (telling a story within a skos definition or schema.org description or something similar).

They want to make it as easy as possible for software consuming the concept resource description, to identify a URL within text, and present a clickable link on a user display.

1.     https://example.com/thisotherthing
2.     <a href=" https://example.com/thisotherthing ">this other thing</a>
3.     other ...

Given that there will be software that isn't interested in rendering clickable links, but is interested in displaying text to a user, they may end up displaying html tags to the user, making the text slightly less legible.

Is there recommended practice for including (or not including) a URL (with or without html tags), within text?  Are there other approaches than those described above?

bye
rowan

[Rob Atkinson]

Note SKOS and RDF allow us to explicitly type text - so

"<something>"@en is text with no links

"""a <a href="example.org/link">Link</a>"""^^rdf:HTML   is HTML text.

skos:prefLabels are supposed to be language tagged plain text

other predicates may have different rules about ranges and these should be respected.

I recommend you define a formal profile with a validator for what you decide to support.

_______________________________________________________   kind regards Rob Atkinson Lead Ontologist, Knowledge Architect at SURROUND Australia Pty Ltd Address   Level 9, Nishi Building, 2 Phillip Law Street; New Acton Canberra Australia 2601 Phone     +61 419 202 973 Email      rob.at...@surroundaustralia.comWebsite   https://www.surroundaustralia.com Enhancing Intelligence Within Organisations delivering evidence that connects decisions to outcomes Copyrights: SURROUND Australia Pty Ltd is the copyright owner of all  original content and attachments. All rights reserved.  Confidentiality Notice: The contents of this e-mail are confidential to the ordinary user  of the e-mail address to which it is addressed, and may also be  privileged. If you are not the addressee of this e-mail, you may  not copy, forward, disclose, or otherwise use it or any part of it  or its attachments in any form whatsoever. If you have received  this e-mail in error, please e-mail the sender by replying to this  message.

--
You received this message because you are subscribed to the Google Groups "AVSIG (Australian Vocabulary Special Interest Group)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to avsig+un...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/avsig/07991e77-7945-4288-abf2-da3f251f958cn%40googlegroups.com.

[Nicholas Car]

The VocPub profile of SKOS states that when you want to indicate some literal value is a hyperlink, you should use a datatype of xsd:anyURI, e.g.

<some-concept-IRI> dcterms:source "https://example.com/thisotherthing"^^xsd:anyURI ;

This is differentiate a hyperlink from text and a hyperlink from an RDF node identified with an IRI, viz. <some-concpet-IRI>.

This WON'T give you a link with different text though, like <a href=" https://example.com/thisotherthing ">this other thing</a> and I understand that sometimes this is necessary. In that case, you could store HTML as Rob suggests, but I question the value of storing HTML like this as RDF is really about data and embedded HTML is about display.

I suggest perhaps using two object values within a Blank Node like this:

<some-concept-IRI> dcterms:source [

    sdo:url "https://example.com/thisotherthing"^^xsd:anyURI ;

    sdo:name "this other thing" ;

] ;

This is then a "logical" (i.e. data) way of storing the values you need - a URL and text - in an association - grouped by the Blank Node - but as individual, typed, data elements - the anyURL and the text value. With this you can till achieve display but also do other things more easily as you have more explicit data, not an embedded HTML micro format.

Cheers,  Nick

------- Original Message -------

To view this discussion on the web, visit https://groups.google.com/d/msgid/avsig/CAOBWeKvhYHMf-h0FwRKXrMHs0kxcqccizwfo2EPQ7yE6GKaKWw%40mail.gmail.com.

[rowan.brownlee]

Thanks Rob and Nick for your reflections and recommendations on this question.  Much appreciated.