<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><span style="color: rgb(17, 17, 17); font-family: 'Helvetica Neue', Helvetica, Arial, Verdana, sans-serif; font-size: 1.1429em;" class="">I’d imagine a package declaration that looks something like this:</span><br class=""><pre style="color: rgb(17, 17, 17); font-size: 16px;" class=""><code class=" coffeescript hljs" style="display: block; padding: 0.5em; color: rgb(51, 51, 51); background-color: rgb(248, 248, 248); background-position: initial initial; background-repeat: initial initial;"><span class="hljs-reserved">import</span> PackageDescription
<span class="hljs-reserved">let</span> package = Package(
<span class="hljs-attribute" style="color: rgb(0, 128, 128);">name</span>: <span class="hljs-string" style="color: rgb(221, 17, 68);">"SwiftString"</span>
<span class="hljs-attribute" style="color: rgb(0, 128, 128);">origin</span>: <span class="hljs-string" style="color: rgb(221, 17, 68);">"org.sadun”</span>
)</code></pre></div></div></blockquote>I imagined not needing the origin, since a package has a URL.</div><div><br class=""></div><div>A package’s URL is its unique ID.</div><div><br class=""></div><div>Now I am aware that the manifest does not include its URL, so there is potential for badness here, so perhaps we should insist that the URL is in the Manifest.</div><div><br class=""></div><div>I haven’t got all my rationale in a concrete form yet, but I’d rather that the URL is the ID and it is the responsibility of the package author to keep the URL accurate. Much like the web. People delete things on the web, they move things on the web. It is the responsibility of the tooling and the community to work around that.</div><br class=""></body></html>