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

Location required for component type extensions? #52

Open
tylerjw opened this issue Mar 18, 2024 · 1 comment
Open

Location required for component type extensions? #52

tylerjw opened this issue Mar 18, 2024 · 1 comment
Labels
documentation This issue describes a problem which can be addressed by documentation rather than a schema change.

Comments

@tylerjw
Copy link

tylerjw commented Mar 18, 2024

From the spec on component.name.type:

If the type is not recognized by the parser,
the component shall be ignored.
(Parsers are permitted to support additional types
as a conforming extension.)

From the spec on component.name.location:

This attribute is required for |component|\ s
that are not of :string:`"interface"` :attribute:`type`.

Do you think this is an intentional interaction? I am working on adding tests to our parser. Maybe location should be required on a closed set of specific types instead of the open set excluding interface?

@mwoehlke mwoehlke added the documentation This issue describes a problem which can be addressed by documentation rather than a schema change. label Mar 18, 2024
@mwoehlke
Copy link
Member

I'm going to claim that the intended meaning is defined component types. That is, more generally, the specification says nothing about the other attributes of a non-defined component type.

If a wording change is desired, it probably makes more sense to clarify in the first quoted paragraph (i.e. at type).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation This issue describes a problem which can be addressed by documentation rather than a schema change.
Projects
None yet
Development

No branches or pull requests

2 participants