Skip to content

[UI] add intro #871

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
edmondchuc wants to merge 5 commits into
base: gh-pages
Choose a base branch
from
+32 −5
Open

[UI] add intro #871

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
f061074
add ui introduction
edmondchuc Apr 27, 2026
fcb1e1e
Update ui scope and some intro fixes
edmondchuc Apr 27, 2026
82f96ad
Update shacl12-ui/index.html
edmondchuc Apr 28, 2026
902e2a7
Update shacl12-ui/index.html
edmondchuc Apr 28, 2026
e1e8176
Update shacl12-ui/index.html
edmondchuc Apr 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 32 additions & 5 deletions shacl12-ui/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -187,15 +187,42 @@ <h2>Document Outline</h2>
<p>Content.</p>
</section>

<section id="introduction">
<section id="introduction" class="appendix informative">
<h2>Introduction</h2>
<p>Content.</p>
<p>
RDF applications commonly provide user interfaces that allow users to view and edit RDF resources.
Copy link
Copy Markdown
Contributor

@robert-david robert-david Apr 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
RDF applications commonly provide user interfaces that allow users to view and edit RDF resources.
RDF applications commonly provide user interfaces that allow users to view and edit RDF graphs.

Copy link
Copy Markdown
Contributor Author

@edmondchuc edmondchuc Apr 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer "resources" here, at least for the moment, since SHACL UI is primarily targeting form rendering and editing of resources. I'd consider "graphs" if the scope of SHACL UI broadens beyond forms.

SHACL Core, together with vocabularies such as DASH, has often been used for this purpose by
describing the structure, constraints, labels, and presentation-relevant metadata associated with
RDF data.
</p>

<p>
SHACL User Interfaces are defined by this specification as a complementary vocabulary and rendering model for
generating forms from SHACL shapes. It introduces UI-specific concepts and processing rules for
determining widgets, resolving labels, and grouping and ordering the form components used to manage
RDF resources.
</p>

<p>
Existing SHACL shapes and RDF data can be used to generate functional forms without additional
SHACL UI annotations. SHACL UI annotations allow authors to provide more specific rendering
information, enabling implementations to generate more tailored and consistent forms.
The goal is to improve interoperability between SHACL-based form generation systems
by defining common behavior across implementations.
</p>

<p>
This specification is intended for RDF application developers, RDF data editors, and authors of SHACL
shapes who wish to generate forms for their data.
</p>

<section id="scope" class="appendix informative">
<h3>Scope</h3>
<p>This specification defines form generation using SHACL Core for viewing and editing RDF resources.
Its scope is limited to the rendering of forms from SHACL Core concepts such as shapes, constraints, and property paths.
It also defines label and language resolution for RDF resources and their predicates, as well as a mechanism for determining the widgets used to render value nodes.
<p>
The scope of this specification is limited to form rendering for viewing and editing RDF resources
using SHACL Core concepts such as shapes, constraints, and property paths. It defines processing
behavior for label and language resolution, field grouping and ordering, and widget determination
for value nodes.
</p>

<p>
Expand Down
Loading