Im #XML-Kurs kamen wir wie üblich auf die Schema-Typen für Datum und Zeit (ggf. optionale Zeitzone). An sich kein Problem:

xs:date = 2025-01-25
xs:time = 23:42:00
xs:dateTime = 2025-01-25T23:42:00
xs:gYear = 2025
xs:gYearMonth = 2025-01

ABER, eher selten gesehen bzw. verwendet:
xs:gMonthDay = --01-25 und nicht einfach 01-25

Konvention nach ISO 8601, wobei -- im Kontext anderer Formatstrings dennoch seltsam erscheint.

Gibt mehr wie:
xs:duration = P1Y2M3D (1 Jahr, 2 Monate, 3 Tage)

#XMLSchema

We are excited to release vscode-xml 0.27.0. There's a new setting to specify which attributes should be treated as file paths for editor features like completion. As well, there a few bug fixes. Thanks, Omar, for contributing a bug fix for this release!

For the full changelog, please see: https://github.com/redhat-developer/vscode-xml/blob/main/CHANGELOG.md#0270-may-27-2024

#VSCode #xml #XMLSchema

So there's this #softwaredevelopment project where I try to take an old #Java project and rewrite it in #CSharp.

Today's little bit: Take the old JUnit test source files (plain old #XML documents) and make sure that NUnit can find them. Then write a small NUnit test that tests all of the files against #XMLSchema. Should be easy, right?

Validator goes "Well *these* two files are OK, but *these* two are invalid."

...the XML files and the Schema were unchanged from the Java project from, like, a decade ago.

Eeenngurrgh.

I'm pretty sure the old Java project had similar tests. Or at least it tried to read the files (which should have raised a validation exception). Why didn't it pick one of these up back in the day?

Behold! The mysteries of XML shall never cease!

#CrazyIdea: an #XmlSchema for representing #CBOR (Concise Binary Object Representation) data.

It sounds dumb but I feel like it would be useful for development and testing of software that consumes or produces CBOR.

As for why not JSON, two reasons:

- XML has comments
- CBOR has a typing system that has no JSON equivalent.

Of course, some custom "CTOR" (Concise Textual Object Representation) would probably be better but XML is already has great tooling.

However, I might attempt some sort of "CTOR" as a #TreeSitter learning exercise.

If it goes well, it might even become the "JSON with comments" we all dreamt of. (it won't)

Hi Folks,

I've just published my personal notes to begin using #GNU #Emacs with #XMLSchema, and being ready to work with #SpeedataPublisher 

#Gemini: gemini://omg.pebcak.club/~freezr/gemlog/2023-03-17-emacs-for-speedata.gmi

#Proxy: http://portal.mozz.us/gemini/omg.pebcak.club/~freezr/gemlog/2023-03-17-emacs-for-speedata.gmi

A big thank you to @op  , without his help this gemlog could not be existing! :flan_hearth:

An #introduction appears to be in order:

#Entrepreneur #Investor #Co-Founder & #CEO of #Altova

District Governor of #Rotary District 7930

You might remember me as the co-author of #XMLSpy

Interests: #MobileAppDevelopment, #Drones, #Tech, #Science, #Space, #IOT, #JSON, #XBRL, #XML, #XPATH, #XQUERY, #XSLT, #XMLSCHEMA, and related technologies

Hobbies:
#Skiing, #Boating, #Traveling, #Reading, #Photography

Un article sur mon blog tellement spécialisé qu'il n'intéressera personne : https://www.bortzmeyer.org/validate-epp.html

#EPP #XML #XMLschema