Skip to content

feat: bootstrap bikeshed#20

Merged
dennisvang merged 18 commits intodevelopmentfrom
feature/bikeshed-scaffolding
Mar 12, 2026
Merged

feat: bootstrap bikeshed#20
dennisvang merged 18 commits intodevelopmentfrom
feature/bikeshed-scaffolding

Conversation

@kburger
Copy link
Copy Markdown
Contributor

@kburger kburger commented Dec 16, 2025

Added an index.bs scaffold to demonstrate the use of bikeshed. Locally this can be run using:

bikeshed spec index.bs output.html

Note that the output is not on par with the existing index.html, because bikeshed is opinionated. With some css we can probably get closer, but that is out of scope for this PR.

Up for discussion:

  • folder/file structure and naming convention (folder per chapter, .md file naming)
  • bikeshed metadata (which keys to use, what values to pick)
  • look-and-feel
  • github action automation (see https://speced.github.io/bikeshed/#gh-action-ci)

todo:

fixes #19 (?)

@kburger kburger mentioned this pull request Dec 16, 2025
@kburger kburger force-pushed the feature/bikeshed-scaffolding branch from 6ac6044 to ceced02 Compare December 16, 2025 12:40
@kburger kburger force-pushed the feature/bikeshed-scaffolding branch from ceced02 to ddc5b6f Compare December 16, 2025 12:41
Comment thread src/introduction/intro.md Outdated
@kburger
Copy link
Copy Markdown
Contributor Author

kburger commented Jan 14, 2026

I'm converting the remaining chapters in this PR to keeps things together.

@kburger kburger marked this pull request as ready for review January 14, 2026 14:46
@kburger
Copy link
Copy Markdown
Contributor Author

kburger commented Jan 14, 2026

@luizbonino and @dennisvang, i'm looking for feedback on setup, naming, and what we're missing out on look and feel.

@dennisvang dennisvang changed the title feat: bootstrap bikeshed with first two chapters feat: bootstrap bikeshed Jan 15, 2026
@dennisvang
Copy link
Copy Markdown
Contributor

dennisvang commented Jan 15, 2026

Hi @kburger, looks good already. :)

Not done reviewing, but some notes for now:

  • I've added some project dependencies for local dev in Specify project dependencies #21. Just a suggestion.
  • One thing I've noticed in the bikeshed output is that a "Conformance" section is generated, near the bottom.
    In the new spec we should probably move the info from the "Compliance" section into that "Conformance" section, and move it to the top somewhere.
  • Would it be possible to convert the tables to markdown too, instead of html? I know this will lead to long lines of text again, but in this case I'm inclined to prefer readability of the raw markdown document.

* add .gitignore

* add minimal pyproject.toml with bikeshed dev dependency

* add uv.lock (showing a preference for using astral-sh/uv to manage python and packages)
@kburger
Copy link
Copy Markdown
Contributor Author

kburger commented Jan 19, 2026

@dennisvang bikeshed support commonmark, which does not include tables (see speced/bikeshed#2857 and speced/bikeshed#1128). When a markdown table is written once, and read many times I agree, but if a table needs frequent updates the maintenance of a markdown table can be cumbersome.

For the conformance section, I think it can be influences by configuration settings. That would be something to investigate.

@dennisvang
Copy link
Copy Markdown
Contributor

@dennisvang bikeshed support commonmark, which does not include tables (see speced/bikeshed#2857 and speced/bikeshed#1128). [...]

Thanks for pointing that out. I was not aware that md tables are not supported.

[...] When a markdown table is written once, and read many times I agree, but if a table needs frequent updates the maintenance of a markdown table can be cumbersome.

Yes you're right.

Copy link
Copy Markdown
Contributor

@dennisvang dennisvang left a comment

Choose a reason for hiding this comment

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

@kburger (and @luizbonino) This looks good, but I've made some minor suggestions in the review comments, e.g. line breaks etc.

In addition, I've moved the html tables from the metadata.md markdown file into separate html files (already committed in 8e15ff0).

I've also compared all new content with that from the original v1.2 html file, word for word. This includes the text from the new markdown files, as well as the RDF from the new ttl files and the tables from the new html files.
(and confirmed that they are indeed identical)

Finally, I've suggested some minor changes to stay as close as possible to the original content, like adding the [RDF] reference and restoring section 1.2.

There's one important decision to be made, regarding the type of publication. See the this comment for details.

Comment thread index.bs
Comment thread index.bs Outdated
<pre class=metadata>
Title: FAIR Data Point
Shortname: fdp
Status: LS
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@luizbonino, @kburger Should the spec be a draft W3C Community Group Report published by the W3C FDP community group?

That would be:

Suggested change
Status: LS
Org: W3C
Group: fdpcg
Status: CG-DRAFT
Level: none
ED: https://specs.fairdatapoint.org/

Also see CG-DRAFT.

UPDATE: I've created speced/bikeshed-boilerplate#193 to register the FDP Community Group as fdpcg.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggestion: use for now the unoficcial specification and use the CG-DRAFT when we start working on v2. Then we need to communicate it with the FDP CG.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

So then it will become a W3C UD for now.

Comment thread src/compliance/compliance.md Outdated
Comment thread src/metadata/metadata.md Outdated
Comment thread src/introduction/intro.md Outdated
Comment thread src/compliance/compliance.md Outdated
Comment thread src/overall-description/overall.md Outdated
Comment thread src/metadata/metadata.md Outdated
Comment thread src/metadata.md
The FDP extends the DCAT model by adding the concept of a `FAIRDataPoint` as a specific type of data service that serves metadata catalogs and metadata records.
The DCAT extensions and other FDP-specific concepts and relations are defined in the FDP ontology (using the namespace prefix `fdp-o`).
In the FDP ontology, the FAIR Data Point is represented by a sub-class of the concept of `MetadataService`.
Figure 4.1 only depicts the properties that are not already inherited from `Data Service` and `Resource`.

This comment was marked as outdated.

Comment thread src/compliance/compliance.md Outdated
@dennisvang
Copy link
Copy Markdown
Contributor

dennisvang commented Feb 10, 2026

[...]

Up for discussion:

  • folder/file structure and naming convention (folder per chapter, .md file naming)
  • [...]

@kburger @luizbonino Personally I would prefer a (more) flat file structure as follows:

src
├── api.md
├── architecture.md
├── compliance.md
├── intro.md
├── metadata.md
├── overall.md
├── tables
│   ├── table-catalog-metadata.html
│   ├── table-fdp-metadata.html
│   └── table-navigation-information.html
└── turtles
    ├── example-metadataservice.ttl
    ├── shacl-catalog.ttl
    └── shacl-fdp.ttl
  • simpler
  • more convenient w.r.t. collapsing/expanding trees in IDEs
  • see what's in src/ at a glance, instead of needing to descend into nested dirs
  • no real need to collect chapters in separate dirs (yet)

What do you think?

dennisvang and others added 6 commits February 10, 2026 14:22
Co-authored-by: Dennis <29799340+dennisvang@users.noreply.github.com>
Co-authored-by: Dennis <29799340+dennisvang@users.noreply.github.com>
Co-authored-by: Dennis <29799340+dennisvang@users.noreply.github.com>
Co-authored-by: Dennis <29799340+dennisvang@users.noreply.github.com>
Co-authored-by: Dennis <29799340+dennisvang@users.noreply.github.com>
Comment thread src/architecture/architecture.md Outdated
Comment thread src/architecture/architecture.md Outdated
Comment thread src/architecture/architecture.md Outdated
Comment thread src/metadata/metadata.md Outdated
Comment thread index.bs Outdated
<pre class=metadata>
Title: FAIR Data Point
Shortname: fdp
Status: LS
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

So then it will become a W3C UD for now.

Comment thread index.bs Outdated
luizbonino and others added 2 commits February 16, 2026 13:30
Co-authored-by: Dennis <29799340+dennisvang@users.noreply.github.com>
* add github build-validate workflow, using the w3c/spec-prod action

* run workflow on pull request and on push to development branch

* prevent duplicate workflows
@dennisvang dennisvang dismissed their stale review February 16, 2026 13:11

already discussed and done

* move markdown files from subdirs into src/ and update index.bs accordingly

* move src/metadata/tables/ to src/tables/ and update refs

* rename src/metadata/ to src/rdf/ and update refs

* fix img tags
* update index.html with bikeshed build

* remove duplicate image and unused images

* remove deprecated style/, scripts/, images/_notes/

* remove deprecated spec.md

* create standalone copies of old versions in separate directories (Basically we just create snapshots of the old versions of the spec, including all relevant resources, in separate directories. This introduces some duplication of resources (images, style, scripts), but it makes each version self-contained. A DRY approach using git history will be considered at a later stage.)

* adapt all links to new file structure and make image links relative to enable simple snapshot copy
@dennisvang dennisvang merged commit 5e122bf into development Mar 12, 2026
1 check passed
@dennisvang dennisvang deleted the feature/bikeshed-scaffolding branch March 12, 2026 10:52
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.

Use the W3C bikeshed tool

3 participants