Comments (6)
Every run of the spec-parser generates an updated ontology in all formats, including the PlantUML diagram.
The generated files should be copied in the ontology
directory.
from spdx-spec.
How we are going to communicate about these "alternatives"? (Like, when to use which source)
- https://spdx.org/rdf/3.0.0/spdx-model.ttl (official)
- https://spdx.github.io/spdx-3-model/model.ttl
- Same file as (?) https://github.com/spdx/spdx-3-model/blob/gh-pages/model.ttl (
gh-pages
branch is suggested in spdx/spdx-3-model README and this exact URL is used in spdx-3-model/serialization/json-ld.md)
- Same file as (?) https://github.com/spdx/spdx-3-model/blob/gh-pages/model.ttl (
- https://github.com/spdx/spdx-spec/blob/development/v3.0.1/ontology/ontology.rdf.ttl
I realized that there should be at least two sources: one is stable (generated at release for public use), another is for development (generated frequently for testing/development).
The stable one should be at spdx.org (1) and all spec/doc should point to that new IRIs.
The question is probably where should be the source for the development.
For example, in spdx-3-model
repo (2) or in spdx-spec
repo (3).
Once decided to pick one, we should delete another to avoid confusion.
Also after that, README and etc should be updated to make it clear that this is unstable.
The current situation is a not very friendly for new comer.
The same concern of having multiple sources of truth (and not keep them updated) that happens here for spdx-spec
repo goes to spdx-3-model
repo as well. See: spdx/spdx-3-model#726
from spdx-spec.
From the tech call - we agreed the ontology directory can be deleted.
The gh-pages version is being generated from model repo.
from spdx-spec.
@zvr - let me know if you agree that it can be deleted
from spdx-spec.
@goneall I admit that I like having a directory where one can see everything as files, as we had until now at https://github.com/spdx/spdx-spec/tree/development/v2.3/ontology
Having the individual files available elsewhere is useful but not equivalent.
But maybe I misunderstood what you wrote. Was the question to me about the ontology
directory here? Or the gh-pages
stuff in spdx-3-model? Reading the minutes it seems only deletion of spdx-3-model/gh-pages
is mentioned.
Anyway, my views:
- delete the spdx-3-model gh-pages stuff
- keep the ontology directory here and populate it with the RDF ontology in different forms, etc.
- also have the diagrams (both automatically generated and hand-curated ones) somewhere in the spdx-spec repo.
(and remember, we still have to generate RDF documentation and publish that one)
from spdx-spec.
If we want to keep this directory, we should have a CI which copies any generated files or original files from the spdx-3-model repo. Doing it manually is leading to omissions and inconsistencies.
from spdx-spec.
Related Issues (20)
- SpecVerion should be SpecVersion
- ABNF grammar of Annex D and case-sensitivity
- Current Version on spdx.dev is still 2.3 HOT 5
- List not displayed correctly in 4.2 RDF Serialization HOT 1
- Wrong display for strikethrough text HOT 1
- Copyright information in mkdocs.yml need an update for v3.
- Deadlinks for /Core/DateTime, /Core/PresenceType, etc. HOT 2
- The SPDX 3.0 HTML page does not have the version selection dropdown HOT 3
- The PDF version of the 3.0 specification is broken HOT 1
- Several TODOs in specification version 3.0.0 HOT 2
- Consider more prominently presenting Annex B in the 3.0 spec documentation
- https://spdx.github.io/spdx-spec/latest/ redirects to v2.3 HOT 1
- publish_common.yml made a reference to non-existing mike version (1.2.0)
- Version selector dropdown: Removing RC versions of the versions with stable release? HOT 3
- Inclusion of Glossary in the spec document? HOT 1
- The software Profile contains the property `None` HOT 1
- The 3.0 spec really want you have the Core tree expanded HOT 3
- The diagrams from the model aren't showing up for the 3.0 spec HOT 2
- Setting up a landing page at https://spdx.github.io to prevent 404
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from spdx-spec.