feat(vocab): setup yml2vocab for managing the LWS vocabulary and json-ld context

[laurensdeb]

This pull request introduces a build system and documentation for the Linked Web Storage Vocabulary, automating the generation of vocabulary artifacts from a YAML source and providing a standards-compliant HTML specification. It includes configuration for GitHub Actions, project dependencies, and initial vocabulary files in multiple formats.

Build automation and workflow setup:

• Added a GitHub Actions workflow (.github/workflows/build-vocab.yml) to automatically build and commit vocabulary artifacts (index.html, vocabulary.ttl, vocabulary.jsonld, vocabulary.context.jsonld) when relevant source files change.
• Added a package.json with a build script using yml2vocab and listed yml2vocab as a development dependency.
• Added .gitignore to exclude node_modules/ from version control.

Vocabulary documentation and specification:

• Added template.html as the ReSpec-based HTML template for generating the vocabulary specification, supporting reserved and deprecated terms, namespaces, and context files.
• Added an auto-generated index.html providing a human-readable, standards-compliant specification for the Linked Web Storage Vocabulary, including property and class definitions, namespace documentation, and context references.

Vocabulary data formats:

• Added a JSON-LD context file (vocabulary.context.jsonld) defining the mapping of vocabulary terms to IRIs and their structure for use with JSON-LD consumers.

Attribution

This PR relies on the yml2vocab tooling which enables this workflow.

[pchampin]

Thanks @laurensdeb this looks great, overall.

One concern, though: I'm generally reluctant to include generated files in the main branch. I would find it cleaner if the provided github action was restricted to GH pages generations.

Eitherway, I think we should have a README in the lws10-vocab folder, listing all the generated files (whether they are commited or not), and providing instructions on how to generate/update them (people will want to see locally the effect of the changes they make to the YAML file or the template).

[ebremer]

I added
'''

• id: as:updated
  label: modified
  domain: lws:DataResource
  range: xsd:dateTime
  comment: The date and time the resource was last modified.

• id: schema:size
  label: size
  domain: lws:DataResource
  range: xsd:long
  comment: The size of the resource in bytes.
  '''
  to the vocabulary.yaml file. The generated files will need an update.

[ebremer]

I added two missing terms and the README.md for which files are auto-generated

[pchampin]

Nipicking: my understanding is that, in yml2vocab, "imported" terms are expected to be described by described_by (pointing to the definition of the term, either in a vocabulary or a specification) rather than comment, which should be used for "local" terms.
@iherman do you confirm? Or am I overinterpreting?

[iherman]

@iherman do you confirm? Or am I overinterpreting?

defined_by can be used for any term, both local and imported. The same for comment. The former is usually a URL, the latter a text.

[pchampin]

@iherman do you confirm? Or am I overinterpreting?

defined_by can be used for any term, both local and imported. The same for comment. The former is usually a URL, the latter a text.

I stand corrected, then. Thx @iherman

[pchampin]

good to go, keeping in mind that eventually, the generated files should be kept out of the repo

[jeswr]

Affiliation information needs to be added - similar to https://github.com/w3c/lws-protocol/pull/111/changes