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

Label Property #67

Open
mcdittmar opened this issue Jan 29, 2025 · 3 comments
Open

Label Property #67

mcdittmar opened this issue Jan 29, 2025 · 3 comments

Comments

@mcdittmar
Copy link
Collaborator

mcdittmar commented Jan 29, 2025

Label

  • an example from the use cases as to when this would be used would help
  • as a free-form text with no ‘role’ or attribute to give it meaning, this definition does not seem very useful
    • if this is for things like Stellar Class, Morphology Class, then I’d expect the value to be from a vocabulary, which would give some context of what the value IS.
      • without this context, the “Label.text” references a column FIELD, and gets a value: Label.text = “M”, what does a user do with this?
  • As an AssignedLabel type (if that is what this is): I’d expect
    • value (string)
    • possibly a source vocabulary (where the value came from).. providing description and allowed set
    • or ucd? or something to provide meaning to what the value/vocabulary IS ( value from a Stellar Class vocabulary ) unless the vocabulary itself provides that info. (eg: src.class)

I don't see this in the implementation examples.

@lmichel
Copy link
Collaborator

lmichel commented Jan 30, 2025

I agree, I'll do it
May be a (optional?) attribute to the Label

@lmichel
Copy link
Collaborator

lmichel commented Feb 18, 2025

This is issue is pended until we decide to either remove the Label class or to connect it with a vocabulary

@lmichel
Copy link
Collaborator

lmichel commented Mar 11, 2025

This property allow to connect labels read in the data table with a vocabulary. This feature (filed - vocab binding) is not supported by the VOtable schema yet. I believe it is useful.
I propose to:

  • add a vocabulary URI to the label.
  • not to add any UCD which would be confusing with FIELD[@ucd]

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