Skip to content

Conversation

@SujataSaurabh
Copy link
Member

This change should not update anything else except context, and may reorder a few things. This is a first step towards #876

This change should not update anything else except context, and may reorder a few things.
@SujataSaurabh SujataSaurabh requested a review from a team as a code owner October 5, 2025 06:26
@github-actions
Copy link

github-actions bot commented Oct 5, 2025

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

"arrayShape": "-1,-1,-1",
"dataType": "sc:Float",
"isArray": true,
"arrayShape": "-1,-1,-1",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: It makes more sense to keep the arrayShape property right after isArray.

"@id": "default/observation.state",
"name": "default/observation.state",
"description": "Column 'observation.state' from the Hugging Face parquet file.",
"arrayShape": "19",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: I think the most meaningful order is dataType, isArray, arrayShape.

"@id": "default/action",
"name": "default/action",
"description": "Column 'action' from the Hugging Face parquet file.",
"arrayShape": "19",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment as above.

"@id": "default/steps",
"name": "default/steps",
"description": "Column 'steps' from the Hugging Face parquet file.",
"arrayShape": "-1,-1",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto

@ccl-core
Copy link
Contributor

ccl-core commented Oct 7, 2025

Hi @SujataSaurabh , thank you for your contribution!
I think it would be nice to do all the changes (context, syntax, ...) in one pass, and to use the migration scripts to do that (so that we keep documentation of everything).

In any case, I think it would make sense to wait to update the 1.1 datasets until we are sure that nothing else is going to change in the 1.1 specs...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants