diff --git a/.gitignore b/.gitignore index 62fdbca..d61b1cb 100644 --- a/.gitignore +++ b/.gitignore @@ -218,3 +218,5 @@ FakesAssemblies/ *.vpwhist *.vtg +# Do not track the VMetaDiscussions folder +VMetaDiscussions/ diff --git a/.htaccess b/.htaccess new file mode 100644 index 0000000..37d840c --- /dev/null +++ b/.htaccess @@ -0,0 +1,3 @@ +RewriteEngine On +RewriteCond %{HTTPS} off +RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} diff --git a/index.html b/index.html index fb4a4a9..d3fc3c0 100644 --- a/index.html +++ b/index.html @@ -1,40 +1,41 @@ + + Version Meta Experimental.0 {VSChemaUnderDef.0}
-

Version Meta
-
- - - Experimental.0 - -
- {VSchemaInDev.0} -
-
-
-
-
-

+

Version Meta

+
+ Version: Experimental.0 {VSchemaInDev.0} +

Summary

- Version Meta is a proposed standard Uniform Resource Locator (URI) tag for version strings. - The tag is meant to convey both human and machine readable information regarding the location of the version schema used to build the version string. + Version Meta is a proposed standard tag for version strings. + The tag is meant to convey both; human and machine readable information, regarding the location of the version schema used to build the version string. All version meta tags will be enclosed in curly braces {} and MUST always immediately precede or follow a version string conforming to the specified schema. See versionschema.org for details on the proposed schema DOM. + The version listed near the top of this page is an example of a well-known schema tag, that tooling can use to lookup the named schema (service location is TBD).

@@ -122,9 +123,12 @@

Version Meta Specification (VersionMeta)

- The key-words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119. + The key-words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. The phrase "Version Meta tag" used herein, - refers to tags used to specify a URI to a Version Schema and should not be confused with other meta tags that may be specified by various version schemes (Build Meta used in SemVer for instance). + refers to tags used to specify a URI to a Version Schema ({https://schemas.versionschema.org/SimpleCounter.xml}), + or a well-known identifier ({SimpleCounter}), + and should not be confused with other meta tags, + that may be specified by various version schemes (Build Meta used in SemVer for instance).

1. @@ -139,7 +143,9 @@

TBD: Different/Alternate delimiters?

3. - Version Meta tags MUST NOT contain any whitespace between the URI and the opening and closing currly braces. + Version Meta tags MUST NOT contain any whitespace, + between the URI or well-known identifier, + and the opening and closing currly braces.

4. There MUST NOT be more than one Version Meta tag associated with any version string. @@ -216,7 +222,8 @@

License

In other words, MIT + tell everyone whether you simply copied the content or modified it.

- Last updated 2018-08-22 23:52 UTC +

Contact: metameister@versionmeta.org

+

Last updated 2020-02-05 11:00 UTC