NVIDIA / NVIDIA/simready-foundation

question on asset processing tools/information

Open
#23 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
88
Forks
18
PR merge metrics
No merged PRs in 30d

Description

Are

aif:core:sceneOptimizerVersion | string | Scene Optimizer version
aif:core:assetValidatorVersion | string | Asset Validator version

valid as attributes of a SimReady asset, or are they metadata associated with the tooling/process that created that asset?
I would like to suggest they are the latter. Their values would not impact any downstream use of the asset - they don't contribute to any simulation usecase.

As such, i wouldnt have expected them to be attributes of the asset. Instead, would that sort of data be better represented in customLayerData or assetInfo, where toolchains might place record of actions performed e.g. "optimizer version, settings, validator version, date validated etc."

Also, is it safe to assume that if assetValidateVersion is included, the asset passed validation?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the SimReady asset definitions for aif:core:sceneOptimizerVersion and aif:core:assetValidatorVersion, then compare the documented roles of customLayerData and assetInfo. The issue is done when the specification clearly states where tool and validation metadata belongs and whether assetValidatorVersion implies that validation passed.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.