openlinksoftware / fct Goto Github PK

OpenLink Faceted Browser

License: Other

Makefile 0.06% Java 0.77% Shell 0.18% M4 0.12% CSS 3.42% HTML 0.80% JavaScript 77.23% XSLT 6.69% PLSQL 6.45% Python 4.27%

fct's Introduction

Hi there 👋

📫 How to reach me: @OpenLink.twitter (Twitter), @kidehen.linkedin (LinkedIn), @openlink.email (Email)
💬 Ask me about ... Knowledge Graph, Linked Data, ODBC, JDBC, Data Connectivity, WebID, Privacy-By-Design, Solid, Read-Write Web
🔭 We are currently working on the free flow of data across personal and enterprise data spaces, without comprising platform independence, performance, or privacy.

Here is an example of a personal profile document, using JSON-LD Notaton that's crucial to that effort. For maximum effect, you are encouraged to install the OpenLink Structured Data Sniffer Browser Extension (for Chrome and other Web Extensions compliant Browsers) or Firefox.

## JSON-LD Start ##

{
  "@context": {
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "foaf": "http://xmlns.com/foaf/0.1/",
    "schema": "http://schema.org/",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "dcterms": "http://purl.org/dc/terms/",
    "xsd": "http://www.w3.org/2001/XMLSchema#",
    "owl": "http://www.w3.org/2002/07/owl#",
    "cert": "http://www.w3.org/ns/auth/cert#"
  },
  "@graph": [
    {
      "@id": "",
      "@type": "foaf:PersonalProfileDocument",
      "foaf:maker": {
        "@id": "#i"
      },
      "foaf:primaryTopic": {
        "@id": "#i"
      }
    },
    {
      "@id": "#i",
      "@type": [
        "schema:Organization",
        "foaf:Organization"
      ],
      "schema:mainEntityOfPage": [
        {
          "@id": ""
        },
        {
          "@id": "https://www.openlinksw.com/"
        },
        {
          "@id": "https://www.linkedin.com/company/27491/"
        },
        {
          "@id": "https://www.twitter.com/OpenLink/"
        }
      ],
      "schema:name": {
        "@type": "rdf:langString",
        "@value": "OpenLink Software"
      },
      "owl:sameAs": [
        {
          "@id": "https://www.linkedin.com/company/27491#this"
        },
        {
          "@id": "https://www.openlinksw.com/#this"
        },
        {
          "@id": "https://www.twitter.com/OpenLink#this"
        }
      ]
    },
    {
      "@id": "",
      "@type": [
        "foaf:Document",
        "schema:WebPage"
      ],
      "dcterms:created": {
        "@type": "xsd:dateTime",
        "@value": "2020-07-12"
      },
      "dcterms:creator": {
        "@id": "#i"
      },
      "schema:mainEntity": {
        "@id": "#i"
      },
      "rdfs:name": {
        "@type": "rdf:langString",
        "@value": "OpenLink Software's Profile Document"
      },
      "foaf:primaryTopic": {
        "@id": "#i"
      }
    }
  ]
}

## JSON-LD End ##

Here is the same Profile Information using RDF-Turtle Notation.

## Turtle Start ##

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix schema: <http://schema.org/> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix cert: <http://www.w3.org/ns/auth/cert#> . 
@prefix : <#> . 

# Profile Document Metadata
<> rdf:type foaf:Document, foaf:PersonalProfileDocument, schema:WebPage, schema:CreativeWork .
<> foaf:maker :i .
<> foaf:primaryTopic :i .
<> schema:mainEntity :i .
<> schema:dateCreated "2020-07-12"^^xsd:dateTime .
<> schema:creator :i .
<> schema:name "OpenLink Software's Profile Document" .

# Personal Information 
:i schema:mainEntityOfPage <> .
:i schema:mainEntityOfPage <https://www.openlinksw.com/> .
:i schema:mainEntityOfPage <https://www.linkedin.com/company/27491/> .
:i schema:mainEntityOfPage <https://www.twitter.com/OpenLink/> .
:i rdf:type schema:Organization, foaf:Organization .
:i schema:name "OpenLink Software" .
:i owl:sameAs <https://www.openlinksw.com/#this> .
:i owl:sameAs <https://www.linkedin.com/company/27491#this> .
:i owl:sameAs <https://www.twitter.com/OpenLink#this> .

## Turtle End ##

fct's People

Contributors

Watchers

Forkers

danielhmills imitko pkleef

fct's Issues

include `git_head` detail in all human-focused version strings

@pkleef @openlink @imitko @smalinin @kidehen @HughWilliams @mitache @IvanMikhailov

Can we please start to include git_head info here (line 2740 of sql/facet_view.sql) and anywhere else st_dbms_ver is displayed/output?

st_build_date doesn't provide any insight into the instance version, only the date of its compilation -- which has no relation to when the st_dbms_ver was set nor when the code being compiled was obtained from the repo. st_dbms_ver is also disconnected from the human/marketing "version", e.g., VOS 7.2.6.1 does not correspond to an st_dbms_ver of 07.20.06.01 nor 07.02.06.01.

Originally posted by @TallTed in #21 (comment)

suggestions for new UI in progress

Originally posted by @TallTed in #6 (comment)

@kidehen /cc @danielhmills

I see... I thought those sentences would appear in the main UI, but I now see they're in a mouseover display tied to the "Retry" button. Looking at this page...

I think the "timeout" and "partial/no results!" info should be much more obvious, perhaps atop the table, maybe as a watermark across the table, and definitely not requiring a mouseover of "Retry" to be revealed.
I think the "Retry" button should be styled as a button. Right now, it looks like advisory text.
The invisible scroll-bar on the right is not obviously present. (I'm used to such things, and it still took me more than a few ticks to comprehend it.) The slider looks like a decoration, not an interactive element.
The Go to: ___ Show 50 51 - 100 of 1494 total < > is challenging. I think something like
```
Show ___ rows, from ___ to ### of ### total  <  >
```
where both ___ and ### are filled in by FCT when delivering a page (including the default row-count and 0 for the others when results are empty), ___ are user editable, and ### are not editable.
I have a giant screen. It's generally worthwhile to limit the width of textual content, because of the way eyes work, but there's no reason not to use the full height of my screen.
Given that the active real estate is part of my open window, the odd clickable box at far-upper-right of my window should actually be at far-right of the active real estate; similarly, the mysterious box it opens should be at far-left of active real estate, not at far-left of my window.
I suggest changing the About... box title from About This Virtuoso Faceted Browser Instance to About this Virtuoso Faceted Browser instance.

More on developing UI

I was writing this for #8, and then it was merged... So this is a follow-on.

Again looking at this page --

A mouseover (especially one that reveals un-copyable text) should never be required to get basic information about a page or its content -- as is now the case for the "Retry" button mouseover. I also flagged this in #7; I'm restating it because it's very important.

Can "total" and "retry" button labels be conditionally changed to —

total (no results yet) --- [retry with longer timeout]

— and —

total (partial results) --- [retry with longer timeout]

— and —

total (complete results)

— with the last having no [retry] button)?

The bar for Entity Rank is not visible

The following code in css/default.css causes to hide the second bar for rank:

866  rnk[title~=Entity] {
867      display: none !important;
868  }

for what purpose it is hidden?

openlinksoftware / fct Goto Github PK

fct's Introduction

Hi there 👋

fct's People

Contributors

Watchers

Forkers

fct's Issues

include `git_head` detail in all human-focused version strings

suggestions for new UI in progress

More on developing UI

The bar for Entity Rank is not visible

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent