128 Matching Annotations
- Feb 2024
-
foxtrot-search.com foxtrot-search.com
-
FoxTrot Search https://foxtrot-search.com/
Search tool for XML and other meta data for macOS
-
- Nov 2023
-
edoc.hu-berlin.de edoc.hu-berlin.de
-
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.
-
- Oct 2023
-
www.topicmaps.org www.topicmaps.org
-
www.loc.gov www.loc.gov
- Sep 2023
-
developer.massive.wiki developer.massive.wiki
-
https://developer.massive.wiki/converting_mediawiki_to_massive_wiki
Peter Kaminski suggested to me for export from MediaWiki to Massive Wiki
-
-
xmpp.org xmpp.org
Tags
Annotators
URL
-
- Aug 2023
-
stackoverflow.com stackoverflow.com
-
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
-
- Jul 2023
-
-
Of course there are perversions like XMI and Microsoft's new formats.
Tags
Annotators
URL
-
-
euclideanspace.com euclideanspace.com
-
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.
-
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.
-
-
-
The representation of objects in terms of XML elements and attributes.
-
The standard mechanisms to link objects within the same file or across files.
-
XMI describes solutions to the above issues by specifying EBNF production rules to create XML documents and Schemas that share objects consistently.
-
Object identity, which allows objects to be referenced from other objects in terms of IDs and UUIDs.
-
-
www.iptc.org www.iptc.org
- Jun 2023
-
www.openmobilealliance.org www.openmobilealliance.org
-
technical.openmobilealliance.org technical.openmobilealliance.org
-
eac.staatsbibliothek-berlin.de eac.staatsbibliothek-berlin.de
-
eac.staatsbibliothek-berlin.de eac.staatsbibliothek-berlin.de
-
www.ead-bibliotheque.fr www.ead-bibliotheque.fr
-
learn.microsoft.com learn.microsoft.com
- May 2023
-
www.bortzmeyer.org www.bortzmeyer.org
-
datatracker.ietf.org datatracker.ietf.org
-
xml.cxml.org xml.cxml.org
Tags
Annotators
URL
-
-
xml.cxml.org xml.cxml.org
Tags
Annotators
URL
-
-
xml.cxml.org xml.cxml.org
Tags
Annotators
URL
-
-
cxml.org cxml.org
-
-
www.loc.gov www.loc.gov
-
correspsearch.net correspsearch.net
-
encoding-correspondence.bbaw.de encoding-correspondence.bbaw.de
-
journals.openedition.org journals.openedition.org
Tags
Annotators
URL
-
-
digiversity.net digiversity.net
-
ovalproject.github.io ovalproject.github.io
-
nvd.nist.gov nvd.nist.gov
- Apr 2023
-
www.lido-schema.org www.lido-schema.org
-
www.w3.org www.w3.org
- Mar 2023
-
music-encoding.org music-encoding.org
Tags
Annotators
URL
-
-
music-encoding.org music-encoding.org
- Jan 2023
-
www.iso.org www.iso.org
-
www.xml.com www.xml.com
Tags
Annotators
URL
-
-
docbook.org docbook.org
-
www.oasis-open.org www.oasis-open.org
-
www.hpl.hp.com www.hpl.hp.com
-
github.com github.com
-
https://github.com/CondeNast/atjson
They're using annotations in this context more like CSS, but instead of adding the markup into the content as is done in HTML and processing it, they've physically separated the text and the markup entirely and are using location within the text to indicate where the formatting should take place.
-
- Dec 2022
-
www.w3.org www.w3.org
Tags
Annotators
URL
-
-
jfhr.me jfhr.me
-
JSON is ubiquitous, more lightweight than XML but still flexible enough to represent any data structure you typically need
-
-
docs.oasis-open.org docs.oasis-open.org
Tags
Annotators
URL
-
- Aug 2022
-
docs.oasis-open.org docs.oasis-open.org
-
www.sitemaps.org www.sitemaps.org
Tags
Annotators
URL
-
- Jun 2022
-
chelseatroy.com chelseatroy.com
-
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.
-
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.
-
-
sabnzbd.org sabnzbd.org
-
- May 2022
-
datatracker.ietf.org datatracker.ietf.org
-
oreillymedia.github.io oreillymedia.github.io
-
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
aelements. / text-decoration: underline; color: purple; } svg|a { / These rules would apply to SVGaelements, but not HTML links. / stroke: purple; } svg| { / These rules apply to all SVG-namespaced elements, but not HTML elements. */ mix-blend-mode: multiply; } ```
-
-
datatracker.ietf.org datatracker.ietf.org
Tags
Annotators
URL
-
-
www.edrlab.org www.edrlab.org
Tags
Annotators
URL
-
-
www.w3.org www.w3.orgEPUB 3.21
Tags
Annotators
URL
-
-
datatracker.ietf.org datatracker.ietf.org
- Apr 2022
-
juris-m.github.io juris-m.github.io
Tags
Annotators
URL
-
-
docs.citationstyles.org docs.citationstyles.org
Tags
Annotators
URL
-
-
info.orcid.org info.orcid.org
Tags
Annotators
URL
-
- Mar 2022
-
www.w3.org www.w3.org
Tags
Annotators
URL
-
-
www.ivoa.net www.ivoa.net
-
-
ivoa.net ivoa.net
-
www.w3.org www.w3.org
Tags
Annotators
URL
-
-
www.xspf.org www.xspf.org
Tags
Annotators
URL
-
-
feeds.buzzsprout.com feeds.buzzsprout.com
-
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)?
Tags
Annotators
URL
-
- Feb 2022
-
developer.mozilla.org developer.mozilla.org
Tags
Annotators
URL
-
- Jan 2022
-
georss.org georss.org
-
- Oct 2021
-
-
Press release announcing XML 1.0 as a W3C Recommendation.
-
- Jul 2021
-
acva2010.cs.drexel.edu acva2010.cs.drexel.edu
-
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.
-
- May 2021
-
discourse.julialang.org discourse.julialang.org
Tags
Annotators
URL
-
- Feb 2021
-
www.xml.com www.xml.com
-
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.
-
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.
Tags
Annotators
URL
-
- Nov 2020
-
wiki.alopex.li wiki.alopex.li
-
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
Tags
Annotators
URL
-
- Oct 2020
-
-
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
endor}?
- 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
-
-
facebook.github.io facebook.github.io
-
Balanced named tags is a critical syntactic feature of the XML-style notation.
-
- Sep 2020
- Jun 2020
-
mw.lojban.org mw.lojban.org
-
XML Topic Maps will be put online in that fashion, and thus, that book will become a living document.
Tags
Annotators
URL
-
- May 2020
-
tei.it.ox.ac.uk tei.it.ox.ac.uk
-
Entire web applications can be written in XQuery (+ XSLT,XHTML, CSS and Javascript)
XQuery for entire applications.
-
- Apr 2020
-
-
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
-
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
-
- Mar 2020
-
www.devever.net www.devever.net
-
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)
-
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
-
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
Dictionary
-
The correct way to express a dictionary in XML is something like this
Correct dictionary in XML:
<root> <item> <key>Name</key> <value>John</value> </item> <item> <key>City</key> <value>London</value> </item> </root> -
Broadly speaking, XML excels at annotating corpuses of text with structure and metadata
The right use of XML
-
XML has no notion of numbers (or booleans, or other data types), any numbers represented are just considered more text
Numbers in XML
-
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
-
-
engineering.instawork.com engineering.instawork.com
-
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))
-
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
-
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
-
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
-
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
-
- Feb 2020
-
blog.loadimpact.com blog.loadimpact.com
-
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.
-
- Jan 2020
-
wiki.gnome.org wiki.gnome.org
Tags
Annotators
URL
-
- May 2019
-
www.geeksforgeeks.org www.geeksforgeeks.org
-
stylesheet
Tags
Annotators
URL
-
-
port.sas.ac.uk port.sas.ac.uk
-
stylesheet
Tags
Annotators
URL
-
-
www.techwalla.com www.techwalla.com
Tags
Annotators
URL
-
-
www.convertcsv.com www.convertcsv.com
-
CSV --> XML conversion tool
-
-
nlp.stanford.edu nlp.stanford.edu
-
Basic XML concepts Stanford NLP Shakespeare exmaple
-
-
www.tutorialspoint.com www.tutorialspoint.com
-
tree structure - address book example
Tags
Annotators
URL
-
-
www.tutorialspoint.com www.tutorialspoint.com
Tags
Annotators
URL
-
- Apr 2019
-
convertcsv.com convertcsv.com
-
-
www.w3schools.com www.w3schools.com
-
- Mar 2017
-
www.kaltura.com www.kaltura.com
-
<category>examples > example1</category>
This example is misleading! I'll try to make this clearer.
- ">" should never be used ">" should be used in its place.
- There should be no spaces between the category name and ">". If you put spaces in, category assigment via bulk XML upload will not work.
Tags
Annotators
URL
-
- Jul 2016
-
www.w3schools.com www.w3schools.com
-
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.
-
- Sep 2015
-
jats4r.org jats4r.org
-
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.
-
