<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (rybesh)</title>
    <link>https://pinboard.in/u:rybesh/public/</link>
    <description>recent bookmarks from rybesh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://llmstxt.org/"/>
	<rdf:li rdf:resource="https://hitchdev.com/strictyaml/why/implicit-typing-removed/"/>
	<rdf:li rdf:resource="https://uri4uri.is4.site/"/>
	<rdf:li rdf:resource="https://www.w3.org/International/questions/qa-address-formats"/>
	<rdf:li rdf:resource="https://www.wwp.neu.edu/research/publications/documentation/other/dates_and_times_in_DH.xhtml"/>
	<rdf:li rdf:resource="https://lists.apache.org/thread/cjwmdkp34mcsn8m4hvt2125mk9nqy3nt"/>
	<rdf:li rdf:resource="https://designsystem.digital.gov/"/>
	<rdf:li rdf:resource="https://www.w3.org/TR/css-values-4/#lh"/>
	<rdf:li rdf:resource="https://www.bobdc.com/articles/rdfstandards/"/>
	<rdf:li rdf:resource="http://www.akomantoso.org/"/>
	<rdf:li rdf:resource="https://dmg.org/pfa/"/>
	<rdf:li rdf:resource="https://www.w3.org/TR/dx-prof-conneg/#motivation"/>
	<rdf:li rdf:resource="https://signposting.org/conventions/#publication_resource"/>
	<rdf:li rdf:resource="https://github.com/duraspace/pcdm/wiki"/>
	<rdf:li rdf:resource="https://id.loc.gov/datatypes/edtf.html"/>
	<rdf:li rdf:resource="http://www.commonsemantics.com/oa/Open%20Annotation%20Data%20Model%20Primer.html"/>
	<rdf:li rdf:resource="https://docs.ogc.org/is/17-003r2/17-003r2.html"/>
	<rdf:li rdf:resource="https://www.w3.org/2020/maps/report"/>
	<rdf:li rdf:resource="https://clig.dev/"/>
	<rdf:li rdf:resource="https://shapetrees.github.io/specification/primer"/>
	<rdf:li rdf:resource="https://ocfl.io/1.0/spec/"/>
	<rdf:li rdf:resource="https://github.com/KhronosGroup/glTF"/>
	<rdf:li rdf:resource="https://www.loc.gov/standards/sourcelist/standard-identifier.html"/>
	<rdf:li rdf:resource="https://www.cogna50usa.org/"/>
	<rdf:li rdf:resource="https://github.com/usnationalarchives/digital-preservation"/>
	<rdf:li rdf:resource="https://tools.ietf.org/html/draft-yasskin-webpackage-use-cases-01"/>
	<rdf:li rdf:resource="https://www.pdfa.org/even-with-ocr-the-mueller-report-pdf-isnt-fully-searchable/"/>
	<rdf:li rdf:resource="https://www.pdfa.org/a-technical-and-cultural-assessment-of-the-mueller-report-pdf/"/>
	<rdf:li rdf:resource="https://github.com/sharedstreets/sharedstreets-ref-system"/>
	<rdf:li rdf:resource="https://www.w3.org/TR/charmod/"/>
	<rdf:li rdf:resource="https://www.w3.org/TR/charmod-norm/"/>
	<rdf:li rdf:resource="http://elliotthauser.com/tzbd/tz-link.htm"/>
	<rdf:li rdf:resource="https://alistapart.com/article/readspec"/>
	<rdf:li rdf:resource="https://tools.ietf.org/html/draft-wilde-registries-01"/>
	<rdf:li rdf:resource="https://github.com/ProseMirror/rfcs/"/>
	<rdf:li rdf:resource="http://kcoyle.blogspot.com/2017/04/if-it-aint-broke.html"/>
	<rdf:li rdf:resource="http://wiki.dublincore.org/index.php/User_Guide/Publishing_Metadata#dcterms:language"/>
	<rdf:li rdf:resource="http://schneegans.de/lv/"/>
	<rdf:li rdf:resource="http://open-services.net/"/>
	<rdf:li rdf:resource="http://webconcepts.info/"/>
	<rdf:li rdf:resource="http://www.linkedmodel.org/doc/2015/SCHEMA_vaem-v2.0"/>
	<rdf:li rdf:resource="https://www.w3.org/TR/webmention/"/>
	<rdf:li rdf:resource="http://www.nchs.ucla.edu/history-standards"/>
	<rdf:li rdf:resource="http://vernacular.io/"/>
	<rdf:li rdf:resource="https://www.mnot.net/blog/2014/06/07/rfc2616_is_dead"/>
	<rdf:li rdf:resource="http://www.w3.org/TR/vocab-duv/"/>
	<rdf:li rdf:resource="http://iiif.io/"/>
	<rdf:li rdf:resource="http://visual.ly/daylight-saving-time-explained"/>
	<rdf:li rdf:resource="http://www.w3.org/TR/ldpatch/"/>
	<rdf:li rdf:resource="http://tools.ietf.org/html/rfc6585"/>
	<rdf:li rdf:resource="http://www.w3.org/TR/scxml/"/>
	<rdf:li rdf:resource="http://www.w3.org/ns/formats/"/>
	<rdf:li rdf:resource="http://tools.ietf.org/html/rfc3986#section-4.4"/>
	<rdf:li rdf:resource="http://www.loc.gov/bibframe/docs/bibframe-profiles.html"/>
	<rdf:li rdf:resource="http://tools.ietf.org/html/draft-ietf-urnbis-urns-are-not-uris-00"/>
	<rdf:li rdf:resource="http://spacetelescope.github.io/understanding-json-schema/"/>
	<rdf:li rdf:resource="http://tools.ietf.org/html/rfc4512#section-2"/>
	<rdf:li rdf:resource="http://groups.csail.mit.edu/ana/Publications/PubPDFs/Tussle%20in%20Cyberspace%20Defining%20Tomorrows%20Internet%202005's%20Internet.pdf"/>
	<rdf:li rdf:resource="http://www.mementoweb.org/guide/howto/"/>
	<rdf:li rdf:resource="http://www.dataprotocols.org/en/latest/data-packages.html"/>
	<rdf:li rdf:resource="http://www.ddialliance.org/"/>
	<rdf:li rdf:resource="http://www.loc.gov/marc/marc-functional-analysis/functional-analysis.html"/>
	<rdf:li rdf:resource="http://wiki.dublincore.org/index.php/Cataloger_Scenarios"/>
	<rdf:li rdf:resource="http://meta.wikimedia.org/wiki/BEACON"/>
	<rdf:li rdf:resource="https://github.com/gbv/beaconspec"/>
	<rdf:li rdf:resource="http://gbv.github.com/beaconspec/beacon.html"/>
	<rdf:li rdf:resource="http://docs.webplatform.org/wiki/Main_Page"/>
	<rdf:li rdf:resource="https://twitter.com/dret/status/241036535946952704"/>
	<rdf:li rdf:resource="http://msgpack.org/"/>
	<rdf:li rdf:resource="http://www.niso.org/publications/isq/2012/v24no2-3/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://llmstxt.org/">
    <title>The /llms.txt file – llms-txt</title>
    <dc:date>2026-03-13T19:01:39+00:00</dc:date>
    <link>https://llmstxt.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[We propose adding a /llms.txt markdown file to websites to provide LLM-friendly content. This file offers brief background information, guidance, and links to detailed markdown files.]]></description>
<dc:subject>ai documentation standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5767b51d06b0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hitchdev.com/strictyaml/why/implicit-typing-removed/">
    <title>The Norway Problem - why StrictYAML refuses to do implicit typing and so should you - HitchDev</title>
    <dc:date>2026-02-22T20:43:13+00:00</dc:date>
    <link>https://hitchdev.com/strictyaml/why/implicit-typing-removed/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The most tragic aspect of this bug, however, is that it is intended behavior according to the YAML 1.2 specification. The real fix requires explicitly disregarding the spec - which is why most YAML parsers have it.

StrictYAML sidesteps this problem by ignoring key parts of the spec.]]></description>
<dc:subject>yaml standards parsing design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0d26e6255116/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:yaml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:parsing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://uri4uri.is4.site/">
    <title>uri4uri</title>
    <dc:date>2026-02-17T22:42:16+00:00</dc:date>
    <link>https://uri4uri.is4.site/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The URI resolver just parses the URI to get the parts, then uses registries and external queries to retrieve information about MIME types, top-level domains and so forth. This data is taken from IANA and Wikidata and is periodically updated.

It accepts any possible URI, including web addresses, email addresses, ISBNs as well as some more obscure schemes such as Gopher.]]></description>
<dc:subject>inls620 web standards uri</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:78c8a3730815/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:uri"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/International/questions/qa-address-formats">
    <title>Address formats around the world</title>
    <dc:date>2026-02-03T13:22:29+00:00</dc:date>
    <link>https://www.w3.org/International/questions/qa-address-formats</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[How do address formats differ around the world, and what are the implications of those differences on the design of forms, databases, ontologies, etc. for the Web?

Address formats vary widely across the globe, with differences in structure, content, and the level of granularity. For authors and developers designing forms, databases, or systems that handle addresses, understanding these variations is crucial to avoid frustrating users from other countries. This article will introduce some of the key differences in address formats around the world and provide guidance on how to design systems that can handle them effectively.

This is not an exhaustive guide but aims to sensitize you to the complexities of international address formats and the challenges they pose for web design. As with personal names, there is no one specific "perfect" solution, but awareness of these differences is the first step toward building more inclusive systems.]]></description>
<dc:subject>addresses standards i18n</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2c918ab793e6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:addresses"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:i18n"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.wwp.neu.edu/research/publications/documentation/other/dates_and_times_in_DH.xhtml">
    <title>Dates and Times in DH An annotated application profile of ISO 8601:2019 for use with TEI and other DH systems</title>
    <dc:date>2026-01-22T00:21:22+00:00</dc:date>
    <link>https://www.wwp.neu.edu/research/publications/documentation/other/dates_and_times_in_DH.xhtml</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The purpose of this document is to give readers information and guidance on how to write dates, times, intervals, and durations, along with any inherent imprecision or uncertainty, such that the representation conforms to ISO 8601:2019, and thus can be used on the TEI when-iso attribute. This document is not intended to be an exhaustive tutorial on ISO 8601:2019, although in large part it could serve as such for many of the features of the standard.]]></description>
<dc:subject>temporal reference standards howto tei</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0cdb8d76062a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:temporal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:howto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tei"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://lists.apache.org/thread/cjwmdkp34mcsn8m4hvt2125mk9nqy3nt">
    <title>Re: &lt;file:/path&gt; is imported as &lt;file:///path&gt;-Apache Mail Archives</title>
    <dc:date>2025-01-07T12:03:54+00:00</dc:date>
    <link>https://lists.apache.org/thread/cjwmdkp34mcsn8m4hvt2125mk9nqy3nt</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In RDF, by definition, all URI are resolved against the base URI and  there is always a base URI of some kind.]]></description>
<dc:subject>rdf uri standard standards semweb inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d69bf7ee762a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:uri"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standard"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semweb"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://designsystem.digital.gov/">
    <title>USWDS: The United States Web Design System | U.S. Web Design System (USWDS)</title>
    <dc:date>2024-07-07T18:38:10+00:00</dc:date>
    <link>https://designsystem.digital.gov/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[USWDS provides principles, guidance, and code to help you design and build accessible, mobile-friendly government websites and digital services.]]></description>
<dc:subject>web design standards government</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:063f2cf6ef70/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:government"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/TR/css-values-4/#lh">
    <title>CSS Values and Units Module Level 4: “lh” relative units</title>
    <dc:date>2024-03-04T21:31:46+00:00</dc:date>
    <link>https://www.w3.org/TR/css-values-4/#lh</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Equal to the computed value of the line-height property of the element on which it is used, converting normal to an absolute length by using only the metrics of the first available font.]]></description>
<dc:subject>css standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:396d656267f8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.bobdc.com/articles/rdfstandards/">
    <title>A brief introduction to RDF, related standards, and what they can do for you</title>
    <dc:date>2023-04-30T15:35:21+00:00</dc:date>
    <link>https://www.bobdc.com/articles/rdfstandards/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The following blog entries give a brief introduction to the RDF data model, the most important of the other W3C standards that build on it, and what people do with those standards.

]]></description>
<dc:subject>rdf standards reference inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:48dfa5bd7f80/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.akomantoso.org/">
    <title>Akoma Ntoso | Akoma Ntoso Site</title>
    <dc:date>2022-12-06T21:09:24+00:00</dc:date>
    <link>http://www.akomantoso.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Akoma Ntoso (“linked hearts” in the Akan language of West Africa) defines a set of simple technology-neutral electronic representations in XML format of parliamentary, legislative and judiciary documents.

The XML schemas of Akoma Ntoso make explicit the structure and semantic components of the digital documents so as to support the creation of high value information services that deliver the power of ICTs and increase efficiency and accountability in parliamentary, legislative and judiciary contexts.]]></description>
<dc:subject>law xml opengov standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:339020b3ef3d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:law"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:xml"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opengov"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://dmg.org/pfa/">
    <title>PFA · Portable Format for Analytics</title>
    <dc:date>2022-10-09T20:16:35+00:00</dc:date>
    <link>https://dmg.org/pfa/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[PFA is an open standard for statistical models, machine learning models and data transformation engines. PFA combines the ease of portability across systems with algorithmic flexibility: models, pre-processing, and post-processing are all functions that can be arbitrarily composed, chained, or built into complex workflows. PFA may be as simple as a raw data transformation or as sophisticated as advanced ML/AI algorithms, all described as a JSON or YAML configuration file.]]></description>
<dc:subject>machinelearning statistics metadata standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:202253b9fe01/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:machinelearning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:statistics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/TR/dx-prof-conneg/#motivation">
    <title>Content Negotiation by Profile</title>
    <dc:date>2022-09-01T15:01:42+00:00</dc:date>
    <link>https://www.w3.org/TR/dx-prof-conneg/#motivation</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document describes how Internet clients may negotiate for content provided by servers based on data profiles to which the content conforms. This is distinct from negotiating by Media Type or Language: a profile may specify the content of information returned, which may be a subset of the information the responding server has about the requested resource, and may be structured in a specific way to meet interoperability requirements of a community of practice.]]></description>
<dc:subject>web standards schema data model</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8ea7a68b063c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:schema"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:model"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://signposting.org/conventions/#publication_resource">
    <title>Conventions - Signposting the Scholarly Web</title>
    <dc:date>2021-03-20T21:28:14+00:00</dc:date>
    <link>https://signposting.org/conventions/#publication_resource</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This page provides an overview of a variety of proposed conventions to be used for the Signposting patterns. ]]></description>
<dc:subject>scholarlycommunication metadata standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5ce6889b3fbf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:scholarlycommunication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/duraspace/pcdm/wiki">
    <title>Home · duraspace/pcdm Wiki</title>
    <dc:date>2021-03-20T21:17:01+00:00</dc:date>
    <link>https://github.com/duraspace/pcdm/wiki</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Portland Common Data Model (PCDM) is a flexible, extensible domain model that is intended to underlie a wide array of repository and DAMS applications. The primary objective of this model is to establish a framework that developers of tools (e.g., Samvera-based engines, such as Hyrax, Hyku, Sufia, and Avalon; Islandora; custom Fedora sites) can use for working with models in a general way, allowing adopters to easily use custom models with any tool. Given this interoperability goal, the initial work has been focused on structural metadata and access control, since these are the key actionable metadata.]]></description>
<dc:subject>metadata repository standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:68fc68f7a22f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:repository"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://id.loc.gov/datatypes/edtf.html">
    <title>Extended Date/Time Format Datatypes Scheme - LC Linked Data Service: Authorities and Vocabularies | Library of Congress</title>
    <dc:date>2021-03-20T21:16:27+00:00</dc:date>
    <link>https://id.loc.gov/datatypes/edtf.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Extended Date/Time Format Datatypes Scheme collects the three different datatypes, one each pertaining to a EDTF level.]]></description>
<dc:subject>time data standards rdf</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:ff42803115d9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.commonsemantics.com/oa/Open%20Annotation%20Data%20Model%20Primer.html">
    <title>Open Annotation Draft Data Model</title>
    <dc:date>2021-02-22T18:48:12+00:00</dc:date>
    <link>http://www.commonsemantics.com/oa/Open%20Annotation%20Data%20Model%20Primer.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document provides an intuitive introduction and guide to the Open Annotation Data Model [OA-DM], an interoperable framework for creating associations between related resources, annotations, using a methodology which conforms to the Architecture of the World Wide Web. This primer explains the fundamental Open Annotation Data Model concepts and provides examples of its use. The primer is intended as a starting point for those wishing to create or use Open Annotation Data Model compliant annotation data.

]]></description>
<dc:subject>annotation standards tutorial linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:86c0beb60ec5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:annotation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:tutorial"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://docs.ogc.org/is/17-003r2/17-003r2.html">
    <title>OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard</title>
    <dc:date>2021-02-14T17:59:33+00:00</dc:date>
    <link>https://docs.ogc.org/is/17-003r2/17-003r2.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This OGC standard describes a GeoJSON [NR2] and JSON-LD [NR3] encoding for Earth Observation (EO) metadata for datasets (granules). ]]></description>
<dc:subject>geojson jsonld standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f1ff2fce8e59/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:geojson"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:jsonld"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/2020/maps/report">
    <title>Report on the Joint W3C-OGC Workshop on Maps for the Web — W3C/OGC Joint Workshop Series on Maps for the Web</title>
    <dc:date>2021-02-14T17:53:53+00:00</dc:date>
    <link>https://www.w3.org/2020/maps/report</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The workshop organizers want to make map viewers on the web better — more usable, accessible, secure, private, and performant — for website visitors and web app users. At the same time, we want to make it easier for web developers and other creators to build those map-based experiences. And we want to make it more natural for cartographers and geospatial researchers to share their content over the web.]]></description>
<dc:subject>web maps standards cartography</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:30d8830c8d32/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:maps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cartography"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://clig.dev/">
    <title>Command Line Interface Guidelines</title>
    <dc:date>2020-12-11T22:23:59+00:00</dc:date>
    <link>https://clig.dev/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[An open-source guide to help you write better command-line programs, taking traditional UNIX principles and updating them for the modern day.]]></description>
<dc:subject>cli unix design standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c6e76abb6eee/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cli"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:unix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://shapetrees.github.io/specification/primer">
    <title>Shape Trees Primer</title>
    <dc:date>2020-11-02T22:16:44+00:00</dc:date>
    <link>https://shapetrees.github.io/specification/primer</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This primer introduces shape trees and describes how Semantic Web Applications use them to consistently interoperate over constellations of data structures organized in resource hierarchies used by protocols such as LDP and Solid.]]></description>
<dc:subject>linkeddata SHACL rdf standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c0f28ee2cb24/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:SHACL"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://ocfl.io/1.0/spec/">
    <title>Oxford Common File Layout Specification</title>
    <dc:date>2020-07-23T22:36:33+00:00</dc:date>
    <link>https://ocfl.io/1.0/spec/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This Oxford Common File Layout (OCFL) specification describes an application-independent approach to the storage of digital objects in a structured, transparent, and predictable manner. It is designed to promote long-term access and management of digital objects within digital repositories.

]]></description>
<dc:subject>digital preservation standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:50739f539651/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:digital"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:preservation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/KhronosGroup/glTF">
    <title>KhronosGroup/glTF: glTF – Runtime 3D Asset Delivery</title>
    <dc:date>2020-07-16T18:22:41+00:00</dc:date>
    <link>https://github.com/KhronosGroup/glTF</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[glTF™ (GL Transmission Format) is a royalty-free specification for the efficient transmission and loading of 3D scenes and models by applications. glTF minimizes both the size of 3D assets, and the runtime processing needed to unpack and use those assets.]]></description>
<dc:subject>3d webgl standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0d3765600a15/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:3d"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webgl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.loc.gov/standards/sourcelist/standard-identifier.html">
    <title>Standard Identifier Source Codes: Source Codes for Vocabularies, Rules, and Schemes (Network Development and MARC Standards Office, Library of Congress)</title>
    <dc:date>2020-02-17T22:38:29+00:00</dc:date>
    <link>https://www.loc.gov/standards/sourcelist/standard-identifier.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Standard Identifier Sources lists standard number or code systems and assigns a code to each database or publication that defines or contains the identifiers. The purpose of these source codes is to enable the type of standard numbers or codes in metadata records to be indicated by a code. For code assignment, general structure, usage, and maintenance guidelines see Source Codes for Vocabularies, Rules, and Schemes.]]></description>
<dc:subject>identifiers standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:280b8943adb9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.cogna50usa.org/">
    <title>Council of Geographic Names Authorities 2017 Richmond</title>
    <dc:date>2020-01-14T00:22:30+00:00</dc:date>
    <link>https://www.cogna50usa.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Council of Geographic Names Authorities (COGNA) is an association of state and federal government agencies representing the official and recognized geographic names authorities in the United States who work to promote national standardization of the names of geographic features for official use throughout the country.   The goal of national standardization is sought through cooperation among federal and state agencies that have responsibilities for administering names of geographic features and cultural entities as mandated by the United States Board on Geographic Names (USBGN).  Standardization is important to eliminate confusion, uncertainty, and misunderstanding which may occur when more than one name is used for the same place or feature, when the same name is applied to different features, or the spelling of a name is inconsistent.  The end result is incalculable savings in time and money by increasing the efficiency of a nation’s government and other institutions.  It can prevent misunderstanding, and just as important, can eliminate the inconsistency that occurs when different agencies try to determine geographic name use.  National standardization also allows a country to exercise its prerogative to establish its own standard names.  This process started in the United States  in 1890 when President Benjamin Harrison signed an Executive Order creating the United States Board on Geographic Names.   The  authority of the Board was expanded by Public Law 242—80 of the 80th Congress: Chapter 330—1st Session; S. 1262, 1947.]]></description>
<dc:subject>geo names standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:5d6ddc65f78e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:geo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:names"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/usnationalarchives/digital-preservation">
    <title>usnationalarchives/digital-preservation: NARA digital preservation file format risk analysis and preservation plans</title>
    <dc:date>2019-10-24T16:03:04+00:00</dc:date>
    <link>https://github.com/usnationalarchives/digital-preservation</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[NARA digital preservation file format risk analysis and preservation plans]]></description>
<dc:subject>preservation data standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:976bd602509c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:preservation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://tools.ietf.org/html/draft-yasskin-webpackage-use-cases-01">
    <title>draft-yasskin-webpackage-use-cases-01 - Use Cases and Requirements for Web Packages</title>
    <dc:date>2019-05-10T01:17:49+00:00</dc:date>
    <link>https://tools.ietf.org/html/draft-yasskin-webpackage-use-cases-01</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[People would like to use content offline and in other situations
   where there isn't a direct connection to the server where the content
   originates.  However, it's difficult to distribute and verify the
   authenticity of applications and content without a connection to the
   network.  The W3C has addressed running applications offline with
   Service Workers ([ServiceWorkers]), but not the problem of
   distribution.

   Previous attempts at packaging web resources (e.g.  Resource Packages
   [3] and the W3C TAG's packaging proposal [4]) were motivated by
   speeding up the download of resources from a single server, which is
   probably better achieved through other mechanisms like HTTP/2 PUSH,
   possibly augmented with a simple manifest of URLs a page plans to use
   [5].  This attempt is instead motivated by avoiding a connection to
   the origin server at all.  It may still be useful for the earlier use
   cases, so they're still listed, but they're not primary.]]></description>
<dc:subject>web standards archives</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1cbe90e02eaf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.pdfa.org/even-with-ocr-the-mueller-report-pdf-isnt-fully-searchable/">
    <title>Even with OCR, the Mueller Report PDF isn't fully searchable | PDF Association</title>
    <dc:date>2019-04-20T21:15:18+00:00</dc:date>
    <link>https://www.pdfa.org/even-with-ocr-the-mueller-report-pdf-isnt-fully-searchable/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[On April 19 we published an analysis of the Mueller report PDF released by the US Department of Justice. Further analysis of the PDF file reveals an additional serious problem.

Even after running OCR software, the report isn't truly searchable.]]></description>
<dc:subject>pdf standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0de3a26287d9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:pdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.pdfa.org/a-technical-and-cultural-assessment-of-the-mueller-report-pdf/">
    <title>A Technical and Cultural Assessment of the Mueller Report PDF | PDF Association</title>
    <dc:date>2019-04-20T21:14:57+00:00</dc:date>
    <link>https://www.pdfa.org/a-technical-and-cultural-assessment-of-the-mueller-report-pdf/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[What can we learn about the Mueller Report from the PDF file released by the Department of Justice (DoJ) on April 18, 2019?

This article offers two things:

a brief, high-level technical assessment of the document, and
a question of culture: why everyone assumes it would be delivered as a PDF file – and would have been shocked otherwise.]]></description>
<dc:subject>pdf standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:03fd987b30e5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:pdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/sharedstreets/sharedstreets-ref-system">
    <title>sharedstreets/sharedstreets-ref-system: Making maps connectable: stable, non-proprietary IDs and data standards for streets</title>
    <dc:date>2019-03-08T16:39:54+00:00</dc:date>
    <link>https://github.com/sharedstreets/sharedstreets-ref-system</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[SharedStreets data standards are a way to uniquely identify street space and connect data related to streets. SharedStreets makes maps connectable, and allows porting of data between different street representations, whether data linked to OpenStreetMap, a city-managed GIS system, or a commercial basemap.

Cities today depend on geographic information systems (GIS) to collect and share street data, but this process requires users to agree on a map, or to use predefined, and often proprietary IDs to describe streets.

This limits the potential for collaboration and data sharing between government agencies, and with the private sector. And use of proprietary maps and identification systems can undermine cities’ ability to use and share critical public information about streets.

SharedStreets provides a global, non-proprietary system for describing streets, designed to incorporate any source of street-linked data. This allows public and private entities to communicate with clarity and precision about streets while ensuring full compatibility with organizations’ internal map data.]]></description>
<dc:subject>gis standards opendata urbanplanning</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:300c297435b0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:gis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opendata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:urbanplanning"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/TR/charmod/">
    <title>Character Model for the World Wide Web 1.0: Fundamentals</title>
    <dc:date>2019-02-04T15:47:47+00:00</dc:date>
    <link>https://www.w3.org/TR/charmod/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The word 'character' is used in many contexts, with different meanings. Human cultures have radically differing writing systems, leading to radically differing concepts of a character. Such wide variation in end user experience can, and often does, result in misunderstanding. This variation is sometimes mistakenly seen as the consequence of imperfect technology. Instead, it derives from the great flexibility and creativity of the human mind and the long tradition of writing as an important part of the human cultural heritage. The alphabetic approach used by scripts such as Latin, Cyrillic and Greek is only one of several possibilities.

EXAMPLE: A character in Japanese hiragana and katakana scripts corresponds to a syllable (usually a combination of consonant plus vowel).

EXAMPLE: Korean Hangul combines symbols for individual sounds of the language into square blocks, each of which represents a syllable. Depending on the user and the application, either the individual symbols or the syllabic clusters can be considered to be characters.

EXAMPLE: In Indic scripts each consonant letter carries an inherent vowel that is eliminated or replaced using semi-regular or irregular ways to combine consonants and vowels into clusters. Depending on the user and the application, either individual consonants or vowels, or the consonant or consonant-vowel clusters can be perceived as characters.

EXAMPLE: In Arabic and Hebrew vowel sounds are typically not written at all. When they are written they are indicated by the use of combining marks placed above and below the consonantal letters.]]></description>
<dc:subject>text writing standards web unicode</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:77806f203275/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:text"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:writing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:unicode"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/TR/charmod-norm/">
    <title>Character Model for the World Wide Web: String Matching</title>
    <dc:date>2019-02-04T15:46:03+00:00</dc:date>
    <link>https://www.w3.org/TR/charmod-norm/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This part of the Character Model for the World Wide Web covers string matching—the process by which a specification or implementation defines whether two string values are the same or different from one another. It describes the ways in which texts that are semantically equivalent can be encoded differently and the impact this has on matching operations important to formal languages (such as those used in the formats and protocols that make up the Web).]]></description>
<dc:subject>unicode text web standards semantics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:90893cdd7af6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:unicode"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:text"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:semantics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://elliotthauser.com/tzbd/tz-link.htm">
    <title>Sources for time zone and daylight saving time data</title>
    <dc:date>2018-05-16T00:06:51+00:00</dc:date>
    <link>http://elliotthauser.com/tzbd/tz-link.htm</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Time zone and daylight saving rules are controlled by individual governments. They are sometimes changed with little notice, and their histories and planned futures are often recorded only fitfully. Here is a summary of attempts to organize and record relevant data in this area.]]></description>
<dc:subject>time data organization standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b7f642a113a4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:organization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://alistapart.com/article/readspec">
    <title>How to Read W3C Specs · An A List Apart Article</title>
    <dc:date>2018-02-20T20:48:08+00:00</dc:date>
    <link>https://alistapart.com/article/readspec</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[When you seek answers, you’re looking for a user manual or user reference guide; you want to use the technology. That’s not the purpose of a W3C specification.  The purpose of a “spec” is to tell programmers who will implement the technology what features it must have, and how they are to be implemented.]]></description>
<dc:subject>standards inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:36c12233ec07/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://tools.ietf.org/html/draft-wilde-registries-01">
    <title>draft-wilde-registries-01 - The Use of Registries</title>
    <dc:date>2017-11-15T18:24:45+00:00</dc:date>
    <link>https://tools.ietf.org/html/draft-wilde-registries-01</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Registries on the Internet and the Web fulfill a wide range of tasks,
   ranging from low-level networking aspects such as packet type
   identifiers, all the way to application-level protocols and
   standards.  This document summarizes some of the reasons of why and
   how to use registries, and how some of them are operated.  It serves
   as a informative reference for specification writers considering
   whether to create and manage a registry, allowing them to better
   understand some of the issues associated with certain design
   discussions.]]></description>
<dc:subject>standards vocabularies inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cde8d3c1a32e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:vocabularies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/ProseMirror/rfcs/">
    <title>ProseMirror/rfcs: ProseMirror RFCs</title>
    <dc:date>2017-09-27T22:13:40+00:00</dc:date>
    <link>https://github.com/ProseMirror/rfcs/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[When making substantial changes to the ProseMirror core modules, we use “request for comments” workflow to formalize the design process and allow the community to join the conversation.

A substantial change may be one that introduces a new feature, deprecates something, or is otherwise complex enough to warrant some attention from the community.

This repository serves as a way to propose such RFCs, and as a log of accepted RFCs, which may be valuable for later reference.]]></description>
<dc:subject>periodo process standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0c3b02f4c01b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:periodo"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:process"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kcoyle.blogspot.com/2017/04/if-it-aint-broke.html">
    <title>Coyle's InFormation: If It Ain't Broke</title>
    <dc:date>2017-04-14T23:50:12+00:00</dc:date>
    <link>http://kcoyle.blogspot.com/2017/04/if-it-aint-broke.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[For the first time in over forty years there is serious talk of a new metadata format for library bibliographic data. This is an important moment.

There is not, however, a consensus within the profession on the need to replace the long-standing MARC record format with something different. A common reply to the suggestion that library data creation needs a new data schema is the phrase: "If it ain't broke, don't fix it." This is more likely to be uttered by members of the cataloging community - those who create the bibliographic data that makes up library catalogs - than by those whose jobs entail systems design and maintenance. It is worth taking a good look at the relationship that catalogers have with the MARC format, since their view is informed by decades of daily encounters with a screen of MARC encoding.]]></description>
<dc:subject>metadata standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f5cf94d1559a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://wiki.dublincore.org/index.php/User_Guide/Publishing_Metadata#dcterms:language">
    <title>dcterms:language</title>
    <dc:date>2017-02-16T15:21:15+00:00</dc:date>
    <link>http://wiki.dublincore.org/index.php/User_Guide/Publishing_Metadata#dcterms:language</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The range of dcterms:language it the class dcterms:LinguisticSystem. All values used with dcterms:language have to be instances of this class. Therefore the property may only be used with non-literal values.]]></description>
<dc:subject>metadata standards linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:f7ca415f4015/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://schneegans.de/lv/">
    <title>BCP 47 Validator</title>
    <dc:date>2017-01-26T13:24:49+00:00</dc:date>
    <link>http://schneegans.de/lv/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This service lets you validate language tags such as de-CH or en-US according to BCP 47 (formerly RFC 4646) and the IANA Language Subtag Registry.]]></description>
<dc:subject>language standards regex</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:962fb04acec3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:regex"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://open-services.net/">
    <title>Open Services for Lifecycle Collaboration</title>
    <dc:date>2016-11-22T18:33:51+00:00</dc:date>
    <link>http://open-services.net/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[OSLC (Open Services for Lifecycle Collaboration) is an open and extensible framework that accelerates innovation by removing integration bottlenecks between all the disparate applications that contribute to the entire product lifecycle. OSLC replaces highly coupled, proprietary, server-to-server replication integrations with uncoupled, standards-based, “write once integrate everywhere” solutions. Building on WWW standards to define a minimal set of capabilities that support the most common integration scenarios, OSLC defines an approach for resource and capability discovery and UI enablement.]]></description>
<dc:subject>linkeddata architecture webservices standards inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:1db3ddcb328a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:webservices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://webconcepts.info/">
    <title>Web Concepts</title>
    <dc:date>2016-08-20T22:55:39+00:00</dc:date>
    <link>http://webconcepts.info/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Web's Uniform Interface is based on a large and growing set of specifications. These specifications establish the shared concepts that providers and consumers of Web services can rely on. Web Concepts is providing an overview of these concepts and of the specifications defining them.]]></description>
<dc:subject>web standards documentation inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d87b6667d856/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.linkedmodel.org/doc/2015/SCHEMA_vaem-v2.0">
    <title>Vocabulary for Attaching Essential Metadata (VAEM) - Version 2.0</title>
    <dc:date>2016-02-23T15:52:28+00:00</dc:date>
    <link>http://www.linkedmodel.org/doc/2015/SCHEMA_vaem-v2.0</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The purpose of VAEM is to provide, by import, a foundation for commonly needed resources for metadata on an ontology.

VAEM stands for "Vocabulary for Attaching Essential Metadata". What VAEM regards as essential metadata is data about dates and times, confidentiality, and other characterisitic qualifiers of the ontology, but also references to where a ontology is documented and where to find ontology registration for governance, attribution and provenance. VAEM makes use of some properties from the DC terms vocabulary using the namespace prefix "dct".]]></description>
<dc:subject>metadata standards linkeddata</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d5840aa0294f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.w3.org/TR/webmention/">
    <title>Webmention</title>
    <dc:date>2016-01-13T13:46:28+00:00</dc:date>
    <link>https://www.w3.org/TR/webmention/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Webmention is a simple way to notify any URL when you link to it on your site. From the receiver's perspective, it's a way to request notifications when other sites link to it.]]></description>
<dc:subject>web standards notification linkeddata periodo</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c9f29563e6a9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:notification"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:periodo"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nchs.ucla.edu/history-standards">
    <title>Welcome to UCLA's National Center for History in the Schools</title>
    <dc:date>2015-12-17T20:53:31+00:00</dc:date>
    <link>http://www.nchs.ucla.edu/history-standards</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[These 1996 revised history standards were the result of nearly four years of intensive work by hundreds of gifted classroom teachers of history; of supervisors, state social studies specialists, and chief state school officers responsible for history in the schools; of dozens of talented and active academic historians in the nation; and of representatives of a broad array of professional and scholarly organizations, civic and public interest groups, parents and individual citizens with a stake in the teaching of history in the schools.

This online version of the National Standards for History presents all elements of the printed edition except for 1) charts and illustrations and 2) the appendix listing contributors and participating organizations. It breaks down the standards into 3 sections, the Historical Thinking Standards, US History Standards and World History Standards.]]></description>
<dc:subject>history education standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:80ccd213cce5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:education"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://vernacular.io/">
    <title>Vernacular — HTML Made Special</title>
    <dc:date>2015-12-17T03:43:20+00:00</dc:date>
    <link>http://vernacular.io/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[“Vernacular HTML” is the growing practice of creating domain-specific data formats using the HTML platform. Its goal is to enable interoperable, specialised data interchange while retaining as much of HTML’s full power as is sensible for the given domain. It is not a technology so much as an incipient body of good practices.]]></description>
<dc:subject>html vocabulary language standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:0f6eb3d44c3f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:vocabulary"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:language"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.mnot.net/blog/2014/06/07/rfc2616_is_dead">
    <title>HTTP/1.1 Specifications</title>
    <dc:date>2015-09-03T12:03:07+00:00</dc:date>
    <link>https://www.mnot.net/blog/2014/06/07/rfc2616_is_dead</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The specifications are:

RFC7230 - HTTP/1.1: Message Syntax and Routing - low-level message parsing and connection management
RFC7231 - HTTP/1.1: Semantics and Content - methods, status codes and headers
RFC7232 - HTTP/1.1: Conditional Requests - e.g., If-Modified-Since
RFC7233 - HTTP/1.1: Range Requests - getting partial content
RFC7234 - HTTP/1.1: Caching - browser and intermediary caches
RFC7235 - HTTP/1.1: Authentication - a framework for HTTP authentication]]></description>
<dc:subject>http reference standards inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:30894949037b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/TR/vocab-duv/">
    <title>Dataset Usage Vocabulary</title>
    <dc:date>2015-06-26T17:56:53+00:00</dc:date>
    <link>http://www.w3.org/TR/vocab-duv/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This vocabulary is meant to fill a niche that helps standardize the way Web published dataset usage be conveyed and shared. At this time is no clear standard way to describe dataset usage on the Web. Without a means to systematically describe dataset usage, searching and conveying techniques are application specific and discovery and collaboration across the Web is more difficult. This vocabulary also recommends and requires data publishers to provide a mechanism of receiving data usage from data consumers in the form of feedback,citation and data correction.

]]></description>
<dc:subject>data description standards linkeddata vocabularies</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8dcfcaba0479/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:vocabularies"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://iiif.io/">
    <title>Home — IIIF | International Image Interoperability Framework</title>
    <dc:date>2015-05-11T13:57:20+00:00</dc:date>
    <link>http://iiif.io/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[IIIF (International Image Interoperability Framework) has the following goals:

To give scholars an unprecedented level of uniform and rich access to image-based resources hosted around the world.
To define a set of common application programming interfaces that support interoperability between image repositories.
To develop, cultivate and document shared technologies, such as image servers and web clients, that provide a world-class user experience in viewing, comparing, manipulating and annotating images.]]></description>
<dc:subject>images standards framework</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:855a8c3fce29/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:images"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:framework"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://visual.ly/daylight-saving-time-explained">
    <title>Daylight saving time explained | Visual.ly</title>
    <dc:date>2014-12-20T22:26:07+00:00</dc:date>
    <link>http://visual.ly/daylight-saving-time-explained</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[I wanted to see the effect of daylight saving time change on sunrise and sunset times. The data was taken from http://www.timeanddate.com and is for Chicago. The figure shows that daylight saving timechange (marked by the DLS lines) keeps the sunrise time pretty much constant throughout the whole year, while making the sunset time change a lot. The spread of sunrise times for the whole year as measured by the standard deviation is 42 minutes, while for sunset times is 1:30 hours. ]]></description>
<dc:subject>time visualization standards inls520 inls201</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:4710359d0e32/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:time"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:visualization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls201"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/TR/ldpatch/">
    <title>Linked Data Patch Format</title>
    <dc:date>2014-10-06T21:33:38+00:00</dc:date>
    <link>http://www.w3.org/TR/ldpatch/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Linked Data Patch Format (LD Patch) defines a language for expressing a sequence of operations to apply to Linked Data resources; it is suitable for use with the HTTP PATCH method.

]]></description>
<dc:subject>linkeddata editing standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:8064a45ba55c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:editing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tools.ietf.org/html/rfc6585">
    <title>RFC 6585 - Additional HTTP Status Codes</title>
    <dc:date>2014-09-30T18:06:28+00:00</dc:date>
    <link>http://tools.ietf.org/html/rfc6585</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document specifies additional HTTP [RFC2616] status codes for a variety of common situations, to improve interoperability and avoid confusion when other, less precise status codes are used.

   Note that these status codes are optional; servers cannot be required
   to support them.  However, because clients will treat unknown status
   codes as a generic error of the same class (e.g., 499 is treated as
   400 if it is not recognized), they can be safely deployed by existing
   servers (see [RFC2616] Section 6.1.1 for more information).]]></description>
<dc:subject>http reference standards inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:824448470ca9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:http"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:reference"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/TR/scxml/">
    <title>State Chart XML (SCXML): State Machine Notation for Control Abstraction</title>
    <dc:date>2014-09-30T17:53:18+00:00</dc:date>
    <link>http://www.w3.org/TR/scxml/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document describes SCXML, or the "State Chart extensible Markup Language". SCXML provides a generic state-machine based execution environment based on CCXML and Harel State Tables.]]></description>
<dc:subject>documentation standards statemachine</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:980d39673850/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:statemachine"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/ns/formats/">
    <title>Unique URIs for File Formats</title>
    <dc:date>2014-06-20T14:51:18+00:00</dc:date>
    <link>http://www.w3.org/ns/formats/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA['http://www.w3.org/ns/formats/Format' is a unique, top-level Class URI for specific file formats. Media types do not uniquely identify file formats (eg, serialization formats for various abstract concepts), because not all specific cases do have distinct media types, instances in this class can be used instead for proper identification.

Although the URI-s themselves refer to non-informational resources (ie, they are abstract identifiers), they can be dereferenced. Dereferencing leads to informational resources in XHTML, RDF/XML, or Turtle equivalents, depending on content negotiation.]]></description>
<dc:subject>rdf uri web identifiers standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3278dad6edb7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rdf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:uri"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tools.ietf.org/html/rfc3986#section-4.4">
    <title>RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax</title>
    <dc:date>2014-06-19T03:06:40+00:00</dc:date>
    <link>http://tools.ietf.org/html/rfc3986#section-4.4</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[When a URI reference refers to a URI that is, aside from its fragment
   component (if any), identical to the base URI (Section 5.1), that
   reference is called a "same-document" reference.  The most frequent
   examples of same-document references are relative references that are
   empty or include only the number sign ("#") separator followed by a
   fragment identifier.]]></description>
<dc:subject>web standards uri</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:945721ad0e4b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:uri"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.loc.gov/bibframe/docs/bibframe-profiles.html">
    <title>BIBFRAME Profiles: Introduction and Specification, Draft - 5 May 2014 (BIBFRAME - Bibliographic Framework Initiative, Library of Congress)</title>
    <dc:date>2014-05-07T02:16:42+00:00</dc:date>
    <link>http://www.loc.gov/bibframe/docs/bibframe-profiles.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A BIBFRAME Profile is primarily a means for an application, e.g. cataloging tool, to guide a cataloger in the creation or modification of a BIBFRAME record. But such Profiles can also be used in other ways such as a formal representation of the constraints associated with a content description standard (e.g. RDA, DACS, etc.) or agreed upon representation for interoperability.

]]></description>
<dc:subject>bibliography metadata standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:95019280c9f9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:bibliography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tools.ietf.org/html/draft-ietf-urnbis-urns-are-not-uris-00">
    <title>draft-ietf-urnbis-urns-are-not-uris-00 - Names are Not Locators and URNs are Not URIs</title>
    <dc:date>2014-04-25T13:21:09+00:00</dc:date>
    <link>http://tools.ietf.org/html/draft-ietf-urnbis-urns-are-not-uris-00</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Experience has shown that identifiers associated with persistent names are quite different from identifiers associated with the locations of objects.  This is especially true when such names are are expected to be stable for a very long time or when they identify large and complex entities.  In order to allow Uniform Resource Names (URNs) to evolve to meet the needs of the Informational Sciences community and other users, this specification separates the syntax for URNs from the generic syntax for Uniform Resource Identifiers (URIs) specified in RFC 3986, updating the latter specification accordingly.]]></description>
<dc:subject>identifiers names uri web standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:623e587e7e47/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:names"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:uri"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://spacetelescope.github.io/understanding-json-schema/">
    <title>Understanding JSON Schema — Understanding JSON Schema 1.0 documentation</title>
    <dc:date>2014-01-17T15:10:52+00:00</dc:date>
    <link>http://spacetelescope.github.io/understanding-json-schema/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[JSON Schema is a powerful tool for validating the structure of JSON data. However, learning to use it by reading its specification is like learning to drive a car by looking at its blueprints. You don’t need to know how an internal combustion engine fits together if all you want to do is pick up the groceries. This book, therefore, aims to be the friendly driving instructor for JSON Schema. It’s for those that want to write it and understand it, but maybe aren’t interested in building their own car—er, writing their own JSON Schema validator—just yet.]]></description>
<dc:subject>json validation standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:3e301cdcca83/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:json"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:validation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tools.ietf.org/html/rfc4512#section-2">
    <title>RFC 4512 - Lightweight Directory Access Protocol (LDAP): Directory Information Models</title>
    <dc:date>2014-01-13T17:19:45+00:00</dc:date>
    <link>http://tools.ietf.org/html/rfc4512#section-2</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A directory entry, a named collection of information, is the basic unit of information held in the Directory.  There are multiple kinds of directory entries. An object entry represents a particular object.  An alias entry provides alternative naming.  A subentry holds administrative and/or operational information.

The set of entries representing the DIB are organized hierarchically in a tree structure known as the Directory Information Tree (DIT).]]></description>
<dc:subject>information organization standards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:b7d789874447/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:information"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:organization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://groups.csail.mit.edu/ana/Publications/PubPDFs/Tussle%20in%20Cyberspace%20Defining%20Tomorrows%20Internet%202005's%20Internet.pdf">
    <title>Tussle in Cyberspace: Deﬁning Tomorrow’s Internet</title>
    <dc:date>2014-01-04T17:52:04+00:00</dc:date>
    <link>http://groups.csail.mit.edu/ana/Publications/PubPDFs/Tussle%20in%20Cyberspace%20Defining%20Tomorrows%20Internet%202005's%20Internet.pdf</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The architecture of the Internet is based on a number of principles, including the self-describing datagram packet, the end-to-end arguments, diversity in technology and global addressing. As the Internet has moved from a research curiosity to a recognized component of mainstream society, new requirements have emerged that suggest new design principles, and perhaps suggest that we revisit some old ones. This paper explores one important reality that surrounds the Internet today: different stakeholders that are part of the Internet milieu have interests that may be adverse to each other, and these parties each vie to favor their particular interests. We call this process “the tussle.” Our position is that accommodating this tussle is crucial to the evolution of the network’s technical architecture. We discuss some examples of tussle, and offer some technical design principles that take it into account.]]></description>
<dc:subject>internet architecture standards economics politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:efbeeb955212/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:economics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.mementoweb.org/guide/howto/">
    <title>Memento Guide: Resource Versioning and Memento</title>
    <dc:date>2013-12-21T22:54:43+00:00</dc:date>
    <link>http://www.mementoweb.org/guide/howto/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Memento protocol is widely supported by web archives. It provides a uniform HTTP-based approach to access Mementos, archived versions of web resources, in distributed web archives around the world. Although the Memento protocol can provide the same uniform interface to access resource versions in systems such as wikis, content management systems, and software versioning systems, its applicability in that realm is not well understood. This document provides clarifications and details various ways in which resource versioning systems can support the Memento protocol. ]]></description>
<dc:subject>versioning standards http</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a742fc71c0a1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:versioning"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:http"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.dataprotocols.org/en/latest/data-packages.html">
    <title>Data Packages — Open Data Protocols - Simple Open Standards for Open Data</title>
    <dc:date>2013-05-23T21:00:31+00:00</dc:date>
    <link>http://www.dataprotocols.org/en/latest/data-packages.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[A Data Package (or DataPackage) is a coherent collection of data and possibly other assets into a single form. It provides the basis for convenient delivery, installation and management of datasets.]]></description>
<dc:subject>opendata data standards description metadata inls520</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:70819106a314/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:opendata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:description"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls520"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.ddialliance.org/">
    <title>Welcome to the Data Documentation Initiative | DDI - Data Documentation Initiative</title>
    <dc:date>2013-05-18T20:33:53+00:00</dc:date>
    <link>http://www.ddialliance.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[The Data Documentation Initiative (DDI) is an effort to create an international standard for describing data from the social, behavioral, and economic sciences. Expressed in XML, the DDI metadata specification now supports the entire research data life cycle. DDI metadata accompanies and enables data conceptualization, collection, processing, distribution, discovery, analysis, repurposing, and archiving.]]></description>
<dc:subject>metadata standards socialscience data sharing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a98ae5e3b1f3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:metadata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:socialscience"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:sharing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.loc.gov/marc/marc-functional-analysis/functional-analysis.html">
    <title>Functional Analysis of MARC 21 (Library of Congress)</title>
    <dc:date>2013-01-03T16:23:03+00:00</dc:date>
    <link>http://www.loc.gov/marc/marc-functional-analysis/functional-analysis.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[In 2001, the Network Development and MARC Standards Office (NDMSO) at the Library of Congress commissioned a study to examine MARC 21 from several perspectives:

the FRBR model
the AACR cataloging code model
a set of user tasks that MARC 21 might logically support
The study used the models from IFLA's Functional Requirements for Bibliographic Records (FRBR) and the related Logical Structure of the Anglo-American Cataloguing Rules and was carried out by the consultant who was largely responsible for those studies, Tom Delsey, of Thomas J. Delsey Consulting. By sponsoring this analysis and making it available, the Network Development and MARC Standards Office and others hoped to use the information when analyzing or making decisions relating to format maintenance, system implementation, and data sharing. As a result, the study has proven to be an important tool for the continuing development of the MARC 21 standards.]]></description>
<dc:subject>FRBR MARC standards modeling</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:a9754b8b5ee0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:FRBR"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:MARC"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://wiki.dublincore.org/index.php/Cataloger_Scenarios">
    <title>Cataloger Scenarios - DCMI_MediaWiki</title>
    <dc:date>2012-11-27T22:08:20+00:00</dc:date>
    <link>http://wiki.dublincore.org/index.php/Cataloger_Scenarios</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[These scenarios are intended to assist catalogers in visualizing how their work might flow in a setting that used RDA Vocabularies and FRBR relationships. The goal here is just to show how these packages of information might fit together and how catalogers can use their knowledge and experience in different contexts.]]></description>
<dc:subject>cataloging rda standards modeling data</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:c01bb1856757/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:cataloging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:rda"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:modeling"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://meta.wikimedia.org/wiki/BEACON">
    <title>Dynamic links to external resources - Meta</title>
    <dc:date>2012-11-27T17:23:48+00:00</dc:date>
    <link>http://meta.wikimedia.org/wiki/BEACON</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Wikipedia and other Wikimedia projects provide a rich variety of links to external resources. This links come in form of selected external links and as links to sources or literature. In general the links are manually selected. However some external sources may be relevant to a large and dynamic number of articles. For this purpose in the German Wikipedia there is a project to dynamically add links to selected sources. This enrichment by links is based on a link dump exchange format called BEACON.]]></description>
<dc:subject>identifiers linking web standards wikipedia</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:4a5ac91c8c1c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wikipedia"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/gbv/beaconspec">
    <title>gbv/beaconspec</title>
    <dc:date>2012-11-27T17:23:32+00:00</dc:date>
    <link>https://github.com/gbv/beaconspec</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This git repository contains a specification of BEACON link dump format to be prepared for publication as Request for Comment (RFC).]]></description>
<dc:subject>identifiers linking web standards wikipedia</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:6a2f6e6d5ec1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wikipedia"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://gbv.github.com/beaconspec/beacon.html">
    <title>Beacon link dump format</title>
    <dc:date>2012-11-27T17:22:52+00:00</dc:date>
    <link>http://gbv.github.com/beaconspec/beacon.html</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[This document specifies Beacon, a data interchange format for large numbers of uniform links.]]></description>
<dc:subject>identifiers linking web standards wikipedia</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:33a7a981768b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:identifiers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:web"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:wikipedia"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://docs.webplatform.org/wiki/Main_Page">
    <title>WebPlatform Docs</title>
    <dc:date>2012-10-08T16:12:24+00:00</dc:date>
    <link>http://docs.webplatform.org/wiki/Main_Page</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Web Platform Docs is a new community-driven site that aims to become a comprehensive and authoritative source for web developer documentation. Even though Web Platform Docs is still in alpha, you can already find lots of valuable content on the site, including information on:

How to use features of the open web, with syntax and examples
What platforms and devices you can use various technologies on
What is the current standardization, stability and implementation status of each technology specification
In the future, Web Platform Docs will include even more content for you to explore such as live code examples, resources for educators and much more. ]]></description>
<dc:subject>documentation standards inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:d58c56d95544/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://twitter.com/dret/status/241036535946952704">
    <title>Twitter / dret: a link relation tells you *why* ...</title>
    <dc:date>2012-09-22T04:03:50+00:00</dc:date>
    <link>https://twitter.com/dret/status/241036535946952704</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[a link relation tells you *why* you might want to follow a link; a media type tells you *what* you find there when following it.]]></description>
<dc:subject>html standards * inls620</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:4e72b15c6bf5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:*"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:inls620"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://msgpack.org/">
    <title>MessagePack: It's like JSON. but fast and small.</title>
    <dc:date>2012-09-17T02:00:23+00:00</dc:date>
    <link>http://msgpack.org/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[MessagePack is an efficient binary serialization format. It lets you exchange data among multiple languages like JSON but it's faster and smaller. For example, small integers (like flags or error code) are encoded into a single byte, and typical short strings only require an extra byte in addition to the strings themselves.

If you ever wished to use JSON for convenience (storing an image with metadata) but could not for technical reasons (encoding, size, speed...), MessagePack is a perfect replacement.]]></description>
<dc:subject>data standards representation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:cabc27cd0052/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:representation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.niso.org/publications/isq/2012/v24no2-3/">
    <title>Spring/Summer 2012 (v.24 no.2/3) - National Information Standards Organization</title>
    <dc:date>2012-09-13T18:50:48+00:00</dc:date>
    <link>http://www.niso.org/publications/isq/2012/v24no2-3/</link>
    <dc:creator>rybesh</dc:creator><description><![CDATA[Special issue of Information Standards Quarterly on Linked Data in Libraries, Archives, and Museums.]]></description>
<dc:subject>linkeddata standards libraries archives museum</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:rybesh/b:2f3df1075855/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:linkeddata"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:libraries"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:rybesh/t:museum"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>