Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MangoObject.identifier #64

Open
mcdittmar opened this issue Jan 29, 2025 · 1 comment
Open

MangoObject.identifier #64

mcdittmar opened this issue Jan 29, 2025 · 1 comment

Comments

@mcdittmar
Copy link
Collaborator

I don’t understand the purpose of this attribute from the description

  • it is a required string in a MangoObject, but has no example or detail of purpose.
  • the architecture diagram includes an ‘Identifier’ block in the ‘finding’ section near registry.. is this related?
  • is this related to Section 2.1.1 GAIA: detection identifier?
  • why isn’t this a Property of the MangoObject?

Note:

  • the MangoObject.xml file has 2 MangoObject instances, the value of the identifier in each is “”, yet section 4.10.1 describes it as a ‘Unique identifier of the MangoObject’.
  • the TAP implementation file maps this to a "IAUNAME" column, described as a "unique SRCID"
    I get the impression that the use case which requires this is not part of the implementations
@lmichel
Copy link
Collaborator

lmichel commented Jan 30, 2025

  • It relates to 2.1.1 GAIA least.
  • It is a property of MangoObject

The xml files are snippet generated to help implementers.

  • They are meant to be completed by the users
  • The snippet generator insert into each collection a dummy item instance. This is why there there are 2 MangoObject in this snippet, one is the associated instance of the other.

IAUNAME is a perfect identifier as defined by MANGO. I do not what the trouble with this.

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

No branches or pull requests

2 participants