%% You should probably cite draft-slevinski-formal-signwriting instead of this I-D.
@techreport{slevinski-signwriting-text-02,
    number =    {draft-slevinski-signwriting-text-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-slevinski-signwriting-text/02/},
    author =    {Stephen E. Slevinski Jr.},
    title =     {{The SignPuddle Standard for SignWriting Text}},
    pagetotal = 35,
    year =      2013,
    month =     nov,
    day =       10,
    abstract =  {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. The SignWriting Text encoding model defines the structures of SignWriting Block Printing. The plain-text mathematical names are explained with tokens and regular expressions patterns. The visual image is supported with SVG and PNG generated by a SignWriting Icon Server. The TrueType Font is experimental and not fully functional. Formal SignWriting strings define a lite ASCII markup to name each sign logogram. The text is defined with regular expressions. The included query language defines several productive searching possibilities. The transformation from query language to regular expression is defined. For Unicode, the current use of the Private Use Area font characters is documented. The state of the TrueType Font is explained. A character proposal for plane 1 is included that is isomorphic with the characters that are currently used by the community. 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 compatibility. 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 unlimited.},
}