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

Suggested values for the type attribute of note #384

Open
katjameden opened this issue Oct 24, 2022 · 2 comments
Open

Suggested values for the type attribute of note #384

katjameden opened this issue Oct 24, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@katjameden
Copy link
Collaborator

While checking the guidelines for valid type attribute values, I noticed that the formal specifications for the element note only specify type attribute sample values (such as narrative and summary).

The values, specific to ParlaMint (speaker, time, vote…) are only shown in the Examples.

These values should be added (or maybe even replaced) to the suggested values specification.

@TomazErjavec TomazErjavec changed the title Suggested values for the type attribute Suggested values for the type attribute of note Oct 30, 2022
@nuriabel
Copy link
Collaborator

nuriabel commented Nov 7, 2022

Hi, we got and error for a , is the problem mentioned in this issue the reason?

ERROR
/mnt/d/UPF/proyecto_parlamint/ParlaMint/Data/ParlaMint-ES-CT/ParlaMint-ES-CT_2018-01-17-0101.xml:103:306: error: text not allowed here; expected element "gap", "incident", "kinesic", "note", "pb", "s" or "vocal"

@TomazErjavec
Copy link
Collaborator

Hi, we got and error for a , is the problem mentioned in this issue the reason?

No, this issue refers to the confusion about the note/@type values, but note/@type is not obligatory anyway, and the values are just recommended, not enforced through the schema.

You seem to be using plain text outside <seg>, at least as far as I can make out from the error message - it would help if you posted the offending snippet of your XML and best just open a separate issue for it.

@TomazErjavec TomazErjavec added the enhancement New feature or request label Mar 3, 2024
@TomazErjavec TomazErjavec added this to the Future milestone Mar 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants