The SignPuddle Standard for SignWriting Text

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-11-09
Replaced by draft-slevinski-formal-signwriting
Stream (None)
Intended RFC status Informational
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Sutton-Slevinski Collaboration                              S. Slevinski
Internet-Draft                                                SignPuddle
Intended status: Informational                         November 09, 2014
Expires: May 13, 2015

              The SignPuddle Standard for SignWriting Text


   For concreteness, because the universal character set is not yet
   universal, and because an international standard for the internet
   community should be documented and stable, this I-D has been released
   with the intention of producing an RFC to document the character use
   and naming conventions of the SignWriting community on the Internet.

   The SignWriting Script is an international standard for writing sign
   languages by hand or with computers.  From education to research,
   from entertainment to religion, SignWriting has proven useful because
   people are using it to write signed languages.  The SignWriting
   Script has two major families: Block Printing for the reader and
   Handwriting for the writer.

   Formal SignWriting uses ASCII strings to name logographic signs.  The
   mathematical names are explained with tokens and regular expression
   patterns.  Symbol keys reference the symbols of the International
   SignWriting Alphabet 2010.  Coordinates define X and Y number values
   for 2-dimensional placement.  Signs are written in a spatial SignBox,
   where each symbol is positioned with a 2-dimension coordinate.  For
   sorting, each sign can have an optional temporal sequence of symbols
   that is outside of the SignBox and the visible text.  Completed signs
   are written sequentially, interspersed with punctuation symbols, to
   form sentences.

   The query language of Formal SignWriting uses a similar lite markup
   to define a variety of searching possibilities.  The spatial SignBox
   can be searched for symbols or ranges of symbols.  For each symbol or
   range, the search can specify if the symbol only needs to be found
   somewhere in the SignBox, or if the symbol needs to be found near
   certain coordinates.  The temporal sequence can be searched for
   starting symbols, written as a sequential list of symbols and ranges
   of symbols.  When searching the temporal sequence, the search results
   will be limited to signs that start with a matching temporal
   sequence.  Each query string is transformed into one or more regular
   expressions.  The regular expressions are used to quickly search
   large amounts of data.

Slevinski                 Expires May 13, 2015                  [Page 1]
Internet-Draft              SignWriting Text               November 2014

   For Unicode, there are several encodings which integrate.  Formal
   SignWriting is UTF-8.  The Unicode 8 specification will include
   characters to name the symbols of the International SignWriting
   Alphabet 2010.  There are 2 separate encodings in the Unicode Private
   Use Area.  The plane 15 encoding is isomorphic with Formal
   SignWriting strings, using 3 characters for each symbol.  The plane
   16 encoding is focused on the symbols only, using 1 character for
   each symbol.

   Three appendices discuss additional topics to the standard.  The
   first discusses the Modern SignWriting theory and example document,
   stable since January 12, 2012.  The second discusses the symbol
   encoding of the International SignWriting Alphabet 2010.  The third
   discusses the SignPuddle Standards: licences, infrastructure, and

   This memo concretely defines a conceptual character encoding map for
   the Internet community.  It is published for reference, examination,
   implementation, and evaluation.  Distribution of this memo is

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 13, 2015.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   ( in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Slevinski                 Expires May 13, 2015                  [Page 2]
Show full document text