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

Make Path_type match xs:AnyUri #322

Closed
wants to merge 2 commits into from
Closed

Make Path_type match xs:AnyUri #322

wants to merge 2 commits into from

Conversation

g1zzm0
Copy link
Collaborator

@g1zzm0 g1zzm0 commented Mar 9, 2024

In V3.1, the path type is changed, so that it does not conform anymore to RFC 8089 (paths in filesystems), but conforms to an URI (i.e., xs:anyURI). Moreover, we also adapt the documentation to refer to XML schema 1.0 instead of 1.1, according to the book.

This was necessary because the type of file has changed from file to 
patch type and the wrong rfc for xml 1.1 any uri was given in the pdf 
specification which was adapted for xml schmea 1.0
matches_RFC_8089_path is no longer needed in Spec
@mristin mristin changed the title Update matchesAnyURI Make Path_type match xs:AnyUri Mar 10, 2024
Copy link
Contributor

@mristin mristin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please see the comments below. There is one presumable unrelated change and one possible typo in the docstring.

@@ -1239,6 +1193,10 @@ class Non_empty_XML_serializable_string(str, DBC):

An attribute with data type "string" shall consist of these characters only:
``^[\x09\x0A\x0D\x20-\uD7FF\uE000-\uFFFD\u00010000-\u0010FFFF]*$``.

Constraint AASd-130 ensures that encoding and interoperability between
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose this needs to go in a separate pull request as it is an unrelated change?

Any string conformant to RFC8089 , the “file” URI scheme (for
relative and absolute file paths)
Any string conformant to RFC 2396 and amended by RFC 2732, the “file” URI scheme
for XSL Schema 1.0 relative and absolute file paths
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
for XSL Schema 1.0 relative and absolute file paths
for XSD 1.0 relative and absolute file paths

I suppose XSL is a typo?

@mristin
Copy link
Contributor

mristin commented Mar 10, 2024

@g1zzm0 please don't forget to change the commit message to the pull request description when you squash & merge (or alternatively, shoot me an email so that I can merge).

@mristin
Copy link
Contributor

mristin commented Mar 10, 2024

I also see that the CI fails -- have you run the formatting on your side?

In the virtual environment, you can simply run:

continuous_integration/precommit.py --overwrite

@mristin
Copy link
Contributor

mristin commented Aug 15, 2024

I'm closing this issue to avoid the confusion. The change from the Path to xs:anyURI is (most probably) expected in V3.1.

@mristin mristin closed this Aug 15, 2024
@mristin mristin deleted the g1zzm0/machesAnyURI branch August 15, 2024 09:29
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

Successfully merging this pull request may close these issues.

2 participants