Add semver to the spec

[dmitrizagidulin]

Would it be possible for us to add Semantic Versioning to the spec? (It would help when looking at various rdf-ext etc libraries, to know which version of the spec they implement.)

(We do something similar with Solid specs, just have a Current spec version: 0.4.0 or something, at the top of the readme)

[k00ni]

What is the status here? For me as a foreign developer, writing a compatible library to this specification, this would help. I assume there are also no changes planned, so the current version is 1.0.0?

[bergos]

Not sure how we wanna handle that. I think the interfaces are finished. But at some places we may need more precise descriptions. There is some room for interpretations, which digit of the sem version is affected by these changes. Maybe we can use 1.0.0rc1 for the current version?

[k00ni]

@bergos wrote:

Maybe we can use 1.0.0rc1 for the current version?

Sounds good.

[k00ni]

A little off topic:
There are many open issues related to topics, which are still discussed. We all really should consider working towards agreements and solving those issues. I know that is easier said than done. But loose ends make it hard for implementers to choose the right path for an implementation.

[k00ni]

When do you plan to publish a version 1.0.0rc1?

[elf-pavlik]

I think it would make sense to schedule group telecon in January to get an idea how plans to participate to what extent and who cares on addressing which issues. After that it can go more async again on github with scheduling telecons on demand.

[elf-pavlik]

We haven't touched it during the conference. I think once we resolve equals() issues and merge pending PRs we can tag 1.0.0rc1