Changes in c850f7a: Updated Concepts.md (markdown)

				Projects/xq/Concepts.md
			
          @@ -26,9 +26,16 @@

                   - Second upload will have its hash checked and verified. On mismatch, will return a **HTTP 409 Conflict**

           - Artifacts can be accessed either publicly or can be hidden behind an **access token**

           - Artifact metadata can be queried (same rules apply as accessing the artifact itself)

          +    - artifact name (without version)

          +    - canonical name (with version)

          +    - version

          +    - description

               - date of upload

               - hashes/checksums

               - size

               - mime type

           - Minimal requirement for uploading/updating artifacts should be a relatively simple `curl` request, to make deployment from basically any platform trivial

          -

          +- Allow creation of artifact indices

          +    - This should be designed as a plugin

          +    - Artifacts can be put into an "index", which is just a group of artifacts

          +    - Each index has a specialized rendering surface, so tools like `npm`, `NuGet` or others can use the index to get a list of all available artifacts (mostly packages in that case)

...	...	@@ -26,9 +26,16 @@
26	26	- Second upload will have its hash checked and verified. On mismatch, will return a HTTP 409 Conflict
27	27	- Artifacts can be accessed either publicly or can be hidden behind an access token
28	28	- Artifact metadata can be queried (same rules apply as accessing the artifact itself)
	29	+ - artifact name (without version)
	30	+ - canonical name (with version)
	31	+ - version
	32	+ - description
29	33	- date of upload
30	34	- hashes/checksums
31	35	- size
32	36	- mime type
33	37	- Minimal requirement for uploading/updating artifacts should be a relatively simple `curl` request, to make deployment from basically any platform trivial
34		-
	38	+- Allow creation of artifact indices
	39	+ - This should be designed as a plugin
	40	+ - Artifacts can be put into an "index", which is just a group of artifacts
	41	+ - Each index has a specialized rendering surface, so tools like `npm`, `NuGet` or others can use the index to get a list of all available artifacts (mostly packages in that case)