tame/tamer/tests/xmli/package/src.xml

<?xml version="1.0"?>
<package xmlns="http://www.lovullo.com/rater"
         xmlns:c="http://www.lovullo.com/calc"
         xmlns:t="http://www.lovullo.com/rater/apply-template">

  Packages aren't actually imported yet,
    but they do need to be represented on the graph for `xmli` derivation.
  Import paths will be canonicalized.

  <import package="first/pkg" />
  <import package="second" />
  <import package="third" />
</package>
tamer: NIR->xmli: Represent package imports This doesn't do the actual hard work yet of resolving and loading a package, but it does place it on the graph and re-derive it into the xmli output. DEV-13708 2023-04-06 22:49:13 -04:00			`<?xml version="1.0"?>`
			`<package xmlns="http://www.lovullo.com/rater"`
			`xmlns:c="http://www.lovullo.com/calc"`
			`xmlns:t="http://www.lovullo.com/rater/apply-template">`

			`Packages aren't actually imported yet,`
			but they do need to be represented on the graph for `xmli` derivation.
tamer: asg: Integrate package CanonicalName This change requires every package to have a canonical name, and performs namespec canonicalization on imports. Since all package names are canonicalized, this opens the door to being able to index package names at import, allowing the object to be shared on the graph and properly reference a package after it has been resolved. Note that the system tests' canonicalization is relative to the hard-coded `/TODO` presently; that will change in the near future once `tamec` generates names from the provided path. DEV-13162 2023-05-04 15:03:14 -04:00			`Import paths will be canonicalized.`

			`<import package="first/pkg" />`
tamer: NIR->xmli: Represent package imports This doesn't do the actual hard work yet of resolving and loading a package, but it does place it on the graph and re-derive it into the xmli output. DEV-13708 2023-04-06 22:49:13 -04:00			`<import package="second" />`
			`<import package="third" />`
			`</package>`