Skip to content

Profiling Introduction #489

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.

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
wants to merge 3 commits into
base: gh-pages
Choose a base branch
from
Open

Profiling Introduction #489

wants to merge 3 commits into from

Conversation

nicholascar
Copy link
Contributor

@nicholascar nicholascar commented Aug 8, 2025

A start on Introduction section of the Profiling document to define & scope it.

This is just a proposed intro setting a scope so please comment here to challenge/add to it.

Viewable at https://raw.githack.com/w3c/data-shapes/profiling-updates/shacl12-profiling/index.html

@nicholascar nicholascar changed the title Introduction Profiles Introduction Aug 8, 2025
@nicholascar nicholascar changed the title Profiles Introduction Profiling Introduction Aug 8, 2025
Copy link
Member

@TallTed TallTed left a comment

Choose a reason for hiding this comment

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

Grammar, punctuation, etc.

@nicholascar nicholascar marked this pull request as ready for review August 11, 2025 12:06
In this definition, the essence of the English word is retained, since a summary or extraction of or from a data object <em>may</em> be an outline of it; for example, a 2D representation of a 3D spatial object. or a statistical summary of a dataset having lots of parts.
</p>
<p>
By definition, SHACL constrains (RDF) data; thus, any data that is valid according to a shapes graph will be a profile of the data graph that was validated. In the case of a shapes graph validating all elements of a data graph, the valid data will be a "null" profile of the data graph, that is identical to it.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
By definition, SHACL constrains (RDF) data; thus, any data that is valid according to a shapes graph will be a profile of the data graph that was validated. In the case of a shapes graph validating all elements of a data graph, the valid data will be a "null" profile of the data graph, that is identical to it.
By definition, SHACL constrains (RDF) data. Therefore, any data that is valid according to a shapes graph will be a profile of the data graph that was validated. If a shapes graph validates all elements of a data graph, the resulting valid data will be a "null" profile of the data graph, meaning it is identical to the original data graph.

<em>A data specification that constrains, extends, combines, or provides guidance or explanation about the use of other data specifications.</em>
</p>
<p>
If a shapes graph is taken to be a "data specification" and it can sensibly be then, in addition to data valid according to a shapes graph being a profile of the data graph validated, the shapes graph itself is a profile of the data model used for the data graph.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
If a shapes graph is taken to be a "data specification" and it can sensibly be then, in addition to data valid according to a shapes graph being a profile of the data graph validated, the shapes graph itself is a profile of the data model used for the data graph.
If a shapes graph is taken to be a "data specification," then not only is the data that is valid according to the shapes graph a profile of the validated data graph, but the shapes graph itself also serves as a profile of the data model used for the data graph.

The W3C's <em>Profiles Vocabulary</em> [[dx-prof]] has defined "data profiling" in the context of <em>specifications</em> or <em>data specifications</em>:
</p>
<p style="padding: 0 50px 0 50px;">
<em>A data specification that constrains, extends, combines, or provides guidance or explanation about the use of other data specifications.</em>
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
<em>A data specification that constrains, extends, combines, or provides guidance or explanation about the use of other data specifications.</em>
<em>A data specification that constrains, extends, combines, or provides guidance or explanation about the use of other data specifications. This definition includes what are sometimes called "application profiles", "metadata application profiles", or "metadata profiles".</em>

Should we add the other variants referred to in the specification?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants