Skip to content

Conversation

@lmichel
Copy link
Collaborator

@lmichel lmichel commented Jan 22, 2026

DAL review correction

Copy link

@gmantele gmantele left a comment

Choose a reason for hiding this comment

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

Appart from the two typos and the confusion about ADQL still being in the diagram, I am fine with this.

doc/model.tex Outdated
\subsection{Property}
\label{sect:Property}
Class holder for a \textit{flavor} of property’ ie: there should be a Property subclass for each \textit{flavor} of Property being hosted. The property types are not limited to “physical or calculated” (eg: flags, assigned labels) This class specifies both type and role of the property, and hosts the property instance itself.
Class holder for a \textit{flavor} of propert, i.e., there should be a Property subclass for each \textit{flavor} of Property being hosted. The property types are not limited to “physical or calculated” (eg: flags, assigned labels) This class specifies both type and role of the property, and hosts the property instance itself.

Choose a reason for hiding this comment

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

The final letter of property is missing. Instead of propert it should be property.

\subsection{Property}
\label{sect:Property}
Class holder for a \textit{flavor} of property’ ie: there should be a Property subclass for each \textit{flavor} of Property being hosted. The property types are not limited to “physical or calculated” (eg: flags, assigned labels) This class specifies both type and role of the property, and hosts the property instance itself.
Class holder for a \textit{flavor} of propert, i.e., there should be a Property subclass for each \textit{flavor} of Property being hosted. The property types are not limited to “physical or calculated” (eg: flags, assigned labels) This class specifies both type and role of the property, and hosts the property instance itself.

Choose a reason for hiding this comment

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

Same comment. I assume that it should property.

Choose a reason for hiding this comment

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

ADQL record is still in there. According to your comment in the Mango-1.0-RFC twiki page, it should not be.

@lmichel lmichel merged commit dae4adc into ivoa-std:pr-1.0 Jan 22, 2026
1 check passed
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.

2 participants