Posted by jpluimers on 2016/04/26
Oh yes, someone finally did it!
Insult your co-workers with snarky O RLY parody book covers!
Source:
via: O RLY Cover Generator: Create parodies of the iconic O’Reilly book covers
URL example:
–jeroen
Posted in Development, Software Development | Leave a Comment »
Posted by jpluimers on 2016/04/26
One of the things you cannot do in XSD, is have string enumerations contain both a key and a value.
But there is a little appinfo trick inside annotation that you can user under some circumstances, for instance when you interpret the XSD:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <xs:simpleType name="event_result"> | |
| <xs:restriction base="xs:string"> | |
| <xs:enumeration value="101"> | |
| <xsd:annotation><xsd:appinfo>Syntax error</xsd:appinfo></xsd:annotation> | |
| </xs:enumeration> | |
| <xs:enumeration value="102"> | |
| <xsd:annotation><xsd:appinfo>Illegal operation</xsd:appinfo></xsd:annotation> | |
| </xs:enumeration> | |
| <xs:enumeration value="103"> | |
| <xsd:annotation><xsd:appinfo>Service not available</xsd:appinfo></xsd:annotation> | |
| </xs:enumeration> | |
| </xs:restriction> | |
| </xs:simpleType> |
appinfo is the application counterpart of documentation: both can contain any xml, but appinfo is aimed at machines, whereas documentation is aimed at humans.
–jeroen
via:
Posted in Development, Software Development, XML, XML/XSD, XSD | Leave a Comment »
The Wiert Corner - irregular stream of stuff 