3 ms·
This reminds me that Apple's Plist[1] is similar too: <array> <dict> <key>CFBundleTypeName</key> <string>ShapeEditDocument<
by ytch 4y ago
This reminds me that Apple's Plist[1] is similar too:
<array>
<dict>
<key>CFBundleTypeName</key>
<string>ShapeEditDocument</string>
<key>LSHandlerRank</key>
<string>Owner</string>
<key>LSItemContentTypes</key>
<array>
<string>com.example.shape-doc</string>
</array>
</dict>
</array>
( Taken from[2] )
Maybe it's common to design XML schema like this at that time?
[1] https://en.wikipedia.org/wiki/Property_list https://en.wikipedia.org/wiki/Property_list
[2] https://github.com/robovm/apple-ios-samples/blob/1f6b14ef6e2bda610ef8f1c93b16bf76b8594fbb/ShapeEditBuildingaSimpleiCloudDocumentApp/ShapeEdit/Info.plist https://github.com/robovm/apple-ios-samples/blob/1f6b14ef6e2...
- i386 4y agoYou’re absolutely correct. That’s how XML was written in the late 1990s.
- retrocryptid 4y agoMight be useful to look at what we did for the VWRAP abstract type system in the late 2000's. We generally eschewed attributes in XML and defined a subset of XML that could be automagically converted between JSON and a previously defined legacy binary format. I'm certainly not saying this is how you should do things, but it's interesting to look at and has the feature that messages in one format (like XML) could be automagically transmogrified into another (like JSON.) https://datatracker.ietf.org/doc/html/draft-ietf-vwrap-type-system-00 https://datatracker.ietf.org/doc/html/draft-ietf-vwrap-type-...