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

Small fixes #576

Closed
ndw opened this Issue Oct 24, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@ndw
Contributor

ndw commented Oct 24, 2018

In the course of revising the spec for #554, I propose to make a couple of changes:

  1. I believe that err:XS0084 incorrectly refers to the p:expand-text attribute where it should refer to the p:inline-expand-text attribute
  2. I propose to remove the constraint that [p:]use-when does not apply within p:inline elements. I think that's just a mistake. If we leave that, then we'll have the same argument about nesting within inlines that got us both [p:]expand-text and [p:]inline-expand-text
  3. I moved p:timeout into the core spec.
  4. I added p:message to the core spec.

(I'm documenting these here so that we can track them if there's discussion; if no one objects, we can just close this issue.)

@gimsieke

This comment has been minimized.

Contributor

gimsieke commented Oct 24, 2018

1, agreed.

Because [p:]use-when expressions will be evaluated statically, I think they equally work in inlines. So yes, I agree with 2.

3, 4: Ok. Should we move the remainder of Steps: An Introduction to the main spec?

@xml-project

This comment has been minimized.

Contributor

xml-project commented Oct 24, 2018

FYI: Just added the xs:anyAtomicType -> QName to "Steps: An Introduction" I do not care to move it to the main specs, but I thought I would be the best plain. Was not aware, @ndw was moving in the opposite direction. Sorry.

@ndw

This comment has been minimized.

Contributor

ndw commented Oct 24, 2018

I'm not sure where the QName section belongs. But I'm going to call that a separate issue and close this one.

@ndw ndw closed this Oct 24, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment