As per the Resolvers spec here:

https://github.com/Azure/device-models-tools/wiki/Resolvers

After x-team review, we need to clarify:

• Federation. Resolving from multiple repos
• Client resolver performance #req
• Owners
• GitHub and JEDI
• Dependencies

"As a customer seeking to use the resolution tools, I have appropriate samples and guidance
to help me be successful."

• Resolve single ID in .NET
• README
• Update docs https://docs.microsoft.com/en-us/azure/iot-pnp/concepts-model-repository#public-models
• Use the .NET parser with the resolver

• create storage account with proper subscription
• configure DNS
• configure HTTPS certs

(repeat for test env)

Scrub across the board, but specifically thinking of a case in the validate command.

x-team sign-off on:

• DTMI -> Path (case sensitive requirements)
• Unique IDs
• Dependencies
• CodeOwners
• Federation

"As an internal partner stakeholder, I have reviewed and signed off on the conventions to be
implemented for model resolution."

• check for incorrect casing in first call param
• check for incorrect casing in parser resolver callback

Support resolution from file based DTDL array + CLI enablement of functionality

"As a customer developing a model to later be submitted to the DMR, I have local tools for
pre-validating my models to increase my confidence that my submission will be accepted."

• Check File/Folder consistency with DTMI
• Check Unique IDs
• Check Dependencies are available
• Check DTDL conformance

This task is to support the following initial settings, which can be optionally passed to the ResolverClient

[ ] - Include dependencies
[ ] - Use pre-computed dependencies if available.

If no settings are provided, the ResolverClient will use sensible default settings.

Questions we need answered

• Separate library rather than incorporating it into the existing service SDKs
• Location of the code
• Namespaces
• Signing process
• Package distribution

"As a customer submitting a model to the DMR, I can see checks as part of the PR process telling
me that if my model is valid or not."

• Check File/Folder consistency with DTMI
• Check Unique IDs
• Check Dependencies are available
• Check DTDL conformance

• Generate expanded file version for each interface
• Upload the file to storage

• Publishing Guidelines

• Resolution sample

• Update existing pnp docs.ms.com

  "As an external or internal customer, I have the documentation I need to use and interact
  with the DMR."

Questions we need answered

• Separate library rather than incorporating it into the existing service SDKs
• Location of the code
• Namespaces
• Signing process
• Package distribution

• access GH from SAW
• DevOps bridge?

"As a customer using IoT Explorer, I can use it to resolve models from the DMR."

PR is approved and ready to merge: Azure/azure-iot-explorer#361

• CLI commands
• IoT Explorer resolves models from the new model repo (using the Node library?)

@rido-min will provide requirements prior to starting the work.

WE should enable CORS in the CDN endopoint to enable browser support.

https://docs.microsoft.com/en-us/azure/cdn/cdn-cors

eg.

easy to validate with web-resolver

Use ADO packages. Manual versioning

• Dotnet Global Tool?
• NuGet Package Feed?

Migrating Public models from Mesh https://github.com/rido-min/azure-dtdl-repository/pull/7
Validation passed, but after merging the push scripts says:

Skipping dtmi/meshsystems/txs_blereader-1.json. It doesn't appear to be a DTDL document.
Skipping dtmi/meshsystems/txs_cellular-1.json. It doesn't appear to be a DTDL document.
Skipping dtmi/meshsystems/txs_cellular-2.json. It doesn't appear to be a DTDL document.
Skipping dtmi/meshsystems/txs_cellular-3.json. It doesn't appear to be a DTDL document.
Skipping dtmi/meshsystems/txs_location-1.json. It doesn't appear to be a DTDL document.

https://github.com/rido-min/azure-dtdl-repository/runs/1197467000?check_suite_focus=true#step:4:13

wondering if the push script should fail if there are json files under dtmi that cannot be uploaded. Without detailed inspection this issue would be difficult to detect.

How many failed resolutions?
What is our SLA attainment over the past whatever time period
How many new models have been published/day/week/month?
Trends for all of this

Others?

"As an internal team member processing incoming PR submissions, I have the tools I need to test, validate and otherwise verify that the model is ready to be accepted into the DMR."

• Check File/Folder consistency with DTMI
• Check Unique IDs
• Check Dependencies are available
• Check DTDL conformance
• Check reserved words
• Check with internal tools PolyCheck

Include instructions to allow external users to submit new models.

• Add instructions to README
• Create external PR playbook
• PR/Issue templates

"As a customer seeking to submit a new model to the DMR, I can easily find help, guidance, and possibly tools to help me prepare and submit my new model(s)."

Certification Tests (Portal and CLI) uses DMR.

Catalog uses the DMR

• Commitment from Jacob to adopt this change

"As a customer using the device certification workflow, I can leverage the DMR to resolve the models my device reports."

As per this spec:

https://github.com/Azure/device-models-tools/wiki/Validation-Pipeline

• Readme will be the spec
• Describe dependecies

The existing Model Repo:

• UX https://devicemodels.azureiotsolutions.com/
• REST https://repo.azureiotrepository.com/Models/dtmi:azure:DeviceManagement:DeviceInformation;1?api-version=2020-05-01-preview
• CLI
• IoT Explorer

Will be shutdown when we start operating the new DMR. We need a plan to cover.

• Deprecation/Sunset dates
• Communicate to internal teams
• Migrate existing models in the public repo
• Provide options to save models in private repos
• Advertise the dates in the current UX/CLI/Explorer
• Communicate to existing users
• Identify breaking changes, and impact on existing customers

"As a customer who has previously used the model repository*, I understand what will happen to those models when the new repository goes live, and I know what steps I have to take (if any) to migrate to it."
* - Until now customers could ONLY use company repos, so this doesn't actually affect models in the public repo.

Prepare comms to tell the partners about the new model repo

• New Model Repo email ready for internal and external partners
• Update Certification requirements
• CSS readiness

"As an external partner using PnP, I have recieved clear communication from Microsoft so I understand exactly what is happening with DMR and how that will affect me."

as described in #42

• Export/Import script
• Validate models in test

"As a customer using existing public models, I know that they are available in the new DMR."

• Create packages
• Investigate publishing to NPM under Microsoft account
• Configure the Actions to consume those packages

EXE to be invoked from the Command line

• uses the parser
• uses the resolver
• Command Line Lib
• CI script

Figure out how to integrate with other Azure IoT SDKs

• Track 2 ??
• decide namespaces
• packaging system (GPR? NuGet?)

Should we have 2 instances of storage set up? Assuming we are using geo redundant storage, can we cut over seamlessly?
Should we set up the CDN to fall through to the GitHub pages (assuming we publish there too) in case of storage outage?
Do we need to do anything to protect against a CDN outage? Probably no
How will we detect that we are down? Will it trigger an ICM alert?

• Update push pipeline to workflow_dispatch trigger, so its an explicit decision.

To support a convenient way to change logger behavior instead of customizing config file.

"As a customer seeking to use the resolution tools, I have appropriate samples and guidance
to help me be successful."

• Resolve single ID in .NET
• README

Compliance sign offs

• SDL
• CELA
• PLR

"As an external or internal customer, I have confidence in the service because I know that it
passed through the required Microsoft pre-deployment checks."

Submit PRs with different models, and edge cases

• Unique IDs
• Dependencies
• Case sensitive DTMIs
• Use IoTEx to resolver
• Use README samples
• AICS test