Skip to content
This repository was archived by the owner on May 28, 2024. It is now read-only.

Conversation

@mjovanovik
Copy link

Hi, I added support for displaying values which represent an URI as links
(anchors) in the HTML table. This way, the values which represent an URI can be browsed directly from the results of the tool, just as users are supposed to in a Linked Data / Semantic Web scenario.

For instance, if we browse this example, the values in the cells are currently displayed as text. The goal is to display them as they are here, so that the user can continue browsing data from other places on the web.

It's a small change, but we believe it may be important.

Added support for displaying values which represent an URI as links
(anchors) in the HTML table.
@JeniT
Copy link
Collaborator

JeniT commented Jun 6, 2013

See JeniT/linked-csv#2. I think this should be done through a deeper change. The specification for Linked CSV should be changed to sniff that the type of a value is a URL. Then the code for parsing the Linked CSV should be changed to perform that sniffing and to type the value as a URL. The existing code will then display the link.

Added support for sniffing values as URIs, whenever the type is not set
explicitly to 'url', but the value is an URI.

Also, I rolled back the previous changes to browser.js which displayed
URI strings as anchors. This is now done by the rest of the code, once
the string is identified to be an URI.
Added an alternative representation of URIs, as full URI strings part of
an anchor tag. The icon representation remains a default, but using a
query string parameter (showUri=true), the URIs can be displayed in a
readable manner.
Added an alternative representation of URIs, as full URI strings part of
an anchor tag. The icon representation remains a default, but using a
query string parameter (showUri=true), the URIs can be displayed in a
readable manner.
Added an alternative representation of URIs, as full URI strings part of
an anchor tag. The icon representation remains a default, but using a
query string parameter (showUri=true), the URIs can be displayed in a
readable manner.
Correcting the way the query string parameter is used and detected.
Using '&' instead of '?', since it cannot be the first query string
parameter.
Correcting the way the query string parameter 'uri=' is being
transferred as a Load URL for CSV files / content. The addition of the
'showUri' query string parameter makes this change necessary. The
original code does not assume usage of other query string parameters
besides the 'uri' parameter.
Changed the default URI display from icons to HTML anchors.
If a user wants to view the URIs as icons, the optional query string
parameter 'showUri' can be used, with the value set to 'false', i.e.
"&showUri=false".
Changed the default URI display from icons to HTML anchors.
If a user wants to view the URIs as icons, the optional query string
parameter 'showUri' can be used, with the value set to 'false', i.e.
"&showUri=false".
Conflict resolution.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants