128 Matching Annotations
  1. Feb 2024
  2. Nov 2023
    1. dass für das Element <head> in der TEI das Attribut @placenicht zur Verfügung steht, mit dem diese Positionierung (analog zu der Position von Randbemerkungen,siehe dazu die entsprechenden Beispiele unten) angegeben werden könnte. Um nicht den Rahmen derTEI-Vorgaben verlassen zu müssen, das Phänomen aber dennoch kodieren zu können, wurde innerhalbdes DTABf-M festgelegt, dass die ggf. abweichende Position von Überschriften anstatt mit @place durchdas im Element <head> verfügbare Attribut @type festgelegt wird. Somit konnte an dieser Stelleein Kompromiss zwischen genereller TEI-Konformität und individueller Expressivität gefunden werden.Vgl. dazu auch Haaf/Thomas 2017, Abs. 49 und Anm. 39.

      Dieser Fallback ist jetzt (bzw. seit 2017 mit Release TEI P5 version 3.2.0, Date: 2017-07-10) nicht mehr notwendig, siehe dazu auch https://github.com/cthomasdta/diss-avhkv/issues/5.

  3. Oct 2023
  4. Sep 2023
  5. Aug 2023
    1. application/xml: data-size: XML very verbose, but usually not an issue when using compression and thinking that the write access case (e.g. through POST or PUT) is much more rare as read-access (in many cases it is <3% of all traffic). Rarely there where cases where I had to optimize the write performance existence of non-ascii chars: you can use utf-8 as encoding in XML existence of binary data: would need to use base64 encoding filename data: you can encapsulate this inside field in XML application/json data-size: more compact less that XML, still text, but you can compress non-ascii chars: json is utf-8 binary data: base64 (also see json-binary-question) filename data: encapsulate as own field-section inside json
  6. Jul 2023
    1. The XMI schema also extends the XML schema so that definitions of objects can be stored. This provives a way to hold a UML model.
    2. XMI is a standard which defines how to serialise object instances. Although XML is a very good way to store information in a tree structured way, it is not object oriented. XMI extends XML to make it object oriented.
    1. The representation of objects in terms of XML elements and attributes.
    2. The standard mechanisms to link objects within the same file or across files.
    3. XMI describes solutions to the above issues by specifying EBNF production rules to create XML documents and Schemas that share objects consistently.
    4. Object identity, which allows objects to be referenced from other objects in terms of IDs and UUIDs.
  7. Jun 2023
  8. May 2023
  9. Apr 2023
  10. Mar 2023
  11. Jan 2023
  12. Dec 2022
    1. JSON is ubiquitous, more lightweight than XML but still flexible enough to represent any data structure you typically need
  13. Aug 2022
  14. Jun 2022
    1. The creator of GraphQL admits this. During his presentation on the library at a Facebook internal conference, an audience member asked him about the difference between GraphQL and SOAP. His response: SOAP requires XML. GraphQL defaults to JSON—though you can use XML.
    2. Conclusion There are decades of history and a broad cast of characters behind the web requests you know and love—as well as the ones that you might have never heard of. Information first traveled across the internet in 1969, followed by a lot of research in the ’70s, then private networks in the ’80s, then public networks in the ’90s. We got CORBA in 1991, followed by SOAP in 1999, followed by REST around 2003. GraphQL reimagined SOAP, but with JSON, around 2015. This all sounds like a history class fact sheet, but it’s valuable context for building our own web apps.
  15. May 2022
    1. To select an element tag or attribute defined in a specific namespace, you declare a namespace prefix with an @namespace rule, then use it in your selector. The namespace is separated from the tag name with a | (vertical bar or pipe) character; if there is no tag name in the selector, use a universal * selector:

      ```css @namespace svg "http://www.w3.org/2000/svg";

      a { / These rules would apply to any a elements. / text-decoration: underline; color: purple; } svg|a { / These rules would apply to SVG a elements, but not HTML links. / stroke: purple; } svg| { / These rules apply to all SVG-namespaced elements, but not HTML elements. */ mix-blend-mode: multiply; } ```

  16. Apr 2022
  17. Mar 2022
    1. Good use of XSLT to style an otherwise boring—and unfriendly—XML document (even though I dislike some of the specifics, like the font-size override).

      The template is here: https://feeds.buzzsprout.com/styles.xsl

      Why did we decide that every static site generator should invent their own ad hoc templating system again, instead just using XSLT, which is already standardized (and browser-native)?

  18. Feb 2022
  19. Jan 2022
  20. Oct 2021
  21. Jul 2021
    1. In other non-dereferenceable contexts, such as XML Schema, the namespace identifier is still a URI, but this is simply an identifier (i.e. a namespace name). There is no intention that this can or should be dereferenced. There is even a separate attribute, , which may contain a dereferenceable URI that does point to a copy of the schema document.

      In XML, there is no intent for a namespace to be dereferenceable.

  22. May 2021
  23. Feb 2021
    1. Other approaches have been created to manage information according to topics, such as the Darwin Information Typing Architecture (DITA), an XML architecture used in the industry for technical documentation.
    2. Although XML has become a lingua franca for publishing and data interchange, its usage has decreased among information technology professionals, who now tend to prefer JSON for data interchange, especially in situations where the data structure is straightforward.
  24. Nov 2020
    1. Conclusions Draw your own. No? Fine. Good Enough: JSON? Protobuf Cap’n Proto Flatbuffers CBOR msgpack Avoid: YAML XML Thrift? BSON

      Alternatives to JSON which are well readable by humans. In short, JSON is still fine and seems like it will be for a long time

  25. Oct 2020
    1. hyperscript is more concise because it's just a function call and doesn't require a closing tag. Using it will greatly simplify your tooling chain.

      I suppose this is also an argument that Python tries to make? That other languages have this con:

      • cons: closing tags make it more verbose / increase duplication and that Python is simpler / more concise because it uses indentation instead of closing delimiters like end or } ?
  26. Sep 2020
  27. Jun 2020
    1. XML Topic Maps will be put online in that fashion, and thus, that book will become a living document.
  28. May 2020
  29. Apr 2020
    1. there was a push for standardisation of “SOAP” (simple object access protocol) APIs

      Standarisation of SOAP brought a lot of good stuff but people found XML cumbersome to read.

      A lot of things being solved in SOAP had to subsequently be re-solved on top of JSON using emerging open-ish standards like Swagger (now OpenAPI) and JSON:API

    2. Most APIs you use, or build will be “REST-ish”.
      • You'll be issuing the same kind of "HTTP requests" as the browser
      • Mostly you'll get JSON responses (sometimes XML)
      • You can describe these APIs as JSON-RPC or XML-RPC
  30. Mar 2020
    1. in XML the ordering of elements is significant. Whereas in JSON the ordering of the key-value pairs inside objects is meaningless and undefined

      XML vs JSON (ordering elements)

    2. XML is a document markup language; JSON is a structured data format, and to compare the two is to compare apples and oranges

      XML vs JSON

    3. dictionary (a piece of structured data) can be converted into n different possible documents (XML, PDF, paper or otherwise), where n is the number of possible permutations of the elements in the dictionary


    4. The correct way to express a dictionary in XML is something like this

      Correct dictionary in XML:

    5. Broadly speaking, XML excels at annotating corpuses of text with structure and metadata

      The right use of XML

    6. XML has no notion of numbers (or booleans, or other data types), any numbers represented are just considered more text

      Numbers in XML

    7. To date, the only XML schemas I have seen which I would actually consider a good use of XML are XHTML and DocBook

      Good use of XML

    1. JSON’s origins as a subset of JavaScript can be seen with how easily it represents key/value object data. XML, on the other hand, optimizes for document tree structures, by cleanly separating node data (attributes) from child data (elements)

      JSON for key/value object data

      XML for document tree structures (clearly separating node data (attributes) from child data (elements))

    2. The advantages of XML over JSON for trees becomes more pronounced when we introduce different node types. Assume we wanted to introduce departments into the org chart above. In XML, we can just use an element with a new tag name
    3. JSON is well-suited for representing lists of objects with complex properties. JSON’s key/value object syntax makes it easy. By contrast, XML’s attribute syntax only works for simple data types. Using child elements to represent complex properties can lead to inconsistencies or unnecessary verbosity.

      JSON works well for list of objects with complex properties. XML not so much

    4. UI layouts are represented as component trees. And XML is ideal for representing tree structures. It’s a match made in heaven! In fact, the most popular UI frameworks in the world (HTML and Android) use XML syntax to define layouts.

      XML works great for displaying UI layouts

    5. XML may not be ideal to represent generic data structures, but it excels at representing one particular structure: the tree. By separating node data (attributes) from parent/child relationships, the tree structure of the data shines through, and the code to process the data can be quite elegant.

      XML is good for representing tree structured data

  31. Feb 2020
    1. The lack of a dynamic scripting language is annoying, though Tsung XML scenarios (again, just like JMeter) can include things like loops and if-statements, so it is actually possible to write all sorts of complicated user scenario “code.” The functionality is there, but the usability is not: few developers like “programming” in XML.
  32. Jan 2020
  33. May 2019
  34. Apr 2019
  35. Mar 2017
    1. <category>examples &gt; example1</category>

      This example is misleading! I'll try to make this clearer.

      1. ">" should never be used ">" should be used in its place.
      2. There should be no spaces between the category name and ">". If you put spaces in, category assigment via bulk XML upload will not work.
  36. Jul 2016
    1. childNodes[0] - the first child of the <title> element (the text node)

      There are no nested childnodes beneath it, so of course the title element is the only one. So choose the first. If there was an element nested beneath it, then childNodes[1] would be functional.

  37. Sep 2015
    1. JATS for Reuse (JATS4R) was formed to provide guidelines and tools to standardise the use of the NISO standard Journal and Archiving Tag Set (JATS) for tagging XML in publishing workflows.