Updated README

Author: ndw

README.org

@@ -1,104 +1,6 @@
 * Saxon XInclude Processor
 :PROPERTIES:
-:CUSTOM_ID: h-A2085245-5C37-47C0-A798-B9BA74A7E5DD
+:CUSTOM_ID: h-CE868C20-B294-4E6F-A808-71029DFE0E4B
 :END:
 
-This is an [[http://www.w3.org/TR/xinclude][XInclude]] processor. It operates on the Saxon data model; it
-is not a streaming processor.
-
-At the Java level, it works like this:
-
-#+BEGIN_SRC java
-XdmNode document = … // You got a document from somewhere, right?
-XInclude xinclude = new XInclude();
-XdmNode expanded = xinclude.expandXIncludes(document);
-#+END_SRC
-
-It supports the ~xmlns~, ~element~, ~text~, ~xpath~, and ~search~ fragment
-identifier schemes.
-
-I tried to build it in an extensible, pluggable way so that new
-schemes could be added with relative ease, but that may be a bit
-aspirational.
-
-* Extension function
-:PROPERTIES:
-:CUSTOM_ID: h-9CC4637B-261F-45DB-8F6B-241DC0E722AF
-:END:
-
-You can use this XInclude implementation from XSLT as an extension
-function. Pass the command line option ~-init:com.nwalsh.xslt.Register~
-to Saxon to register the extension function. (If you’re running Saxon
-in some other context, arrange to have the function registered).
-
-In your stylesheet, declare the extension namespace:
-
-#+BEGIN_SRC xml
-<?xml version="1.0" encoding="utf-8"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-
-                xmlns:ext="http://nwalsh.com/xslt"
-
-                xmlns:xs="http://www.w3.org/2001/XMLSchema"
-                exclude-result-prefixes="ext xs"
-                version="3.0">
-#+END_SRC
-
-Then you can call the extension function:
-
-#+BEGIN_SRC xml
-<xsl:sequence select="ext:xinclude($node, $options)"/>
-#+END_SRC
-
-You can use ~function-available()~ to code more defensively. The options
-map is a map from QName keys to values. Only two keys are recognized:
-~fixup-xml-base~ and ~fixup-xml-lang~, both in no namespace. The default
-value for each is “true”. You can omit the second argument entirely if
-you’re happy with those defaults.
-
-** Command line example
-:PROPERTIES:
-:CUSTOM_ID: h-38B19AEE-42B0-4828-A637-5E146C8334D7
-:END:
-
-You can use the ~xinclude.xsl~ file included in the distribution to
-expand the XIncludes in a document.
-
-The trickiest part, as usual with Java applications, is arranging for
-the correct classpath. You need to include the Saxon jar file, the
-SInclude jar file, and any other jars that are necessary for
-dependencies (for example, the XML Resolver jar files for Saxon 11+).
-
-If you have downloaded Saxon HE 11.5 and unzipped it into the
-directory ~saxon~, the following classpath will work:
-
-#+BEGIN_SRC
-export CLASSPATH=saxon/saxon-he-11.5.jar\
-:saxon/lib/xmlresolver-4.6.4.jar\
-:build/libs/sinclude-4.2.1.jar
-#+END_SRC
-
-On Windows, the syntax is different. And you may find it more
-convienent to run from a shell script. The actual transformation is:
-
-#+BEGIN_SRC
-java -cp $CLASSPATH net.sf.saxon.Transform \
-     -init:com.nwalsh.xslt.Register \
-     -xsl:src/test/resources/xinclude.xsl \
-     -s:input-document.xml -o:output-docuent.xml 
-#+END_SRC
-
-The =-init:= option will make sure that Saxon can find and use the
-extension function.
-
-* XPointer schemes
-:PROPERTIES:
-:CUSTOM_ID: h-38009E5E-7A17-49A7-9857-22D7201BB1D8
-:END:
-
-The standard [[https://www.w3.org/TR/xptr-xmlns/][xmlns()]] and [[https://www.w3.org/TR/xptr-element/][element()]] schemes are supported for XML parsing. An
-xpath() scheme is also supported. It evaluates an XPath expression against the document.
-
-For text documents, [[https://tools.ietf.org/html/rfc5147][RFC 5147]] fragment identifiers are supported. My
-own “[[https://norman.walsh.name/2016/09/29/search][search]]” scheme is also supported. The GitHub scheme: L​/start/-L​/end/
-(for example ~L5-L10~ for lines 5-10) is also supported.
+This project has [https://codeberg.org/ndw/sinclude][moved to Codeberg].