XSL-List Guidelines

This information is posted to the XSL-List (and the XSL-List Digest) at int=
ervals under the subject line "XSL-List guidelines".

INTRODUCTION TO XSL-LIST

XSL-List hosts discussion of XSL itself, XSL applications and implementatio=
n, and XSL user questions. XSL-List is open to everyone, users and develope=
rs, experts and novices alike. There is no restriction to what may be poste=
d on the XSL-List provided it is related to XSL, which is considered to inc=
lude XSLT, XPath, and XSL Formatting Objects (FO).

XSL-List is not a W3C mailing list, and has no affiliation with W3C (or any=
 official standing with any standards organization). However, XSL-List was =
established with the encouragement of members of the W3C XSL Working Group,=
 and members of the Working Group are among the subscribers to the list.

Only subscribers may post to XSL-List, but since the goal is to increase th=
e level of XSL knowledge, XSL-List is being archived for everybody to view.=
 The topics being discussed on the XSL-List change as new ideas arise or ex=
isting problems are dealt with, but the archive contains all of the ideas a=
nd solutions that have been discussed on the list.

XSL-List is provided by Mulberry Technologies, Inc., as a service to the XS=
L user community. Mulberry is an XML and SGML consultancy specializing in a=
pplications that have a text design, processing, interchange, or display co=
mponent. For more information about Mulberry Technologies, Inc. see http://=
www.mulberrytech.com=20


SUBSCRIBING TO THE XSL-LIST

To subscribe to the list, fill out the form at http://www.mulberrytech.com/=
lists/subscribe-unsubscribe.html.


DAILY DIGEST

Daily digests -- copies of a whole days XSL-List messages sent as one email=
 message -- are available. Not only is it a single email message containing=
 all of that day's XSL-List messages, it is also half the size, on average,=
 of the individual messages since it doesn't include the overhead of the ma=
il headers from each message.

To subscribe to the digest, use the form at http://www.mulberrytech.com/lis=
ts/subscribe-unsubscribe.html, fill out the forms that are presented, respo=
nd to the emailed confirmation message, and after your subscription is succ=
essful select =E2=80=9CMy Settings=E2=80=9D and click the box beside =E2=80=
=9CDaily Digests=E2=80=9D.=20=20


POSTING GUIDELINES

Only subscribers can post to XSL-List, and only from the exact address they=
 used when they subscribed.

There is no restriction on what may be posted to the XSL-List provided it i=
s related to XSL. Items concerning XML but without a direct connection to X=
SL should be posted to a XML-related list instead of to the XSL-List. Items=
 related to DSSSL should be posted to the DSSSList.

Do not begin your subject line with "help" or "subscribe" since the list so=
ftware will bounce the message because it looks like is an administrative r=
equest.

It is best to start a new message for a new thread. Do not start a new thre=
ad by replying to an unrelated message and just changing the subject line, =
since the header of your message will contain references to the previous me=
ssage and your new message will appear in the archive as one of the replies=
 to the original message.

Both subscribers to the full list ([email protected]) and sub=
scribers to the digest should post their messages to xsl- [email protected]=
rytech.com; the messages will be received by both subscribers to the list a=
nd subscribers to the digest.


BEFORE YOU POST ... DO YOUR HOMEWORK
- Check that your question isn't already answered in the XSL-List archives =
at http://www.biglist.com/lists/xsl-list/archives/.
- If you are asking for help with XSL code, determine which version of the =
language you are using (plus extensions, if any), and confirm that your XSL=
 processor supports that version and/or extension. (If you are unsure of yo=
ur processor, this can be determined by using the stylesheet at http://www.=
mulberrytech.com/xsl/xsl-list/processor-version.xsl on any input, including=
 the stylesheet itself: see http://www.mulberrytech.com/xsl/xsl-list/proces=
sor-version.html for more information.) An XSLT 1.0 engine will not process=
 stylesheets written in XSLT 2.0!


IN YOUR POSTING ...

Name the XSL processor, processor version, and version of the language you =
are using. This information is frequently necessary to diagnose a problem e=
xactly, and always helps respondents give good advice.

If you are replying to a post, trim the quoted message to just the parts to=
 which you are replying.

In addition to following simple rules of net etiquette and common sense, yo=
u will improve the chances that you will receive prompt and helpful respons=
es by:
- Asking questions specific enough that answers are possible. Describe what=
 you are trying to do, how you approached it, what happened, and why you do=
n't like the result you got. Don't simply say "it gave me an error": paste =
in the error message (someone else can probably make sense of it).
-  Illustrating your question with a demonstration of the problem. Well-com=
posed questions frequently include a small XML sample, an XSLT stylesheet, =
the results received, and the result that was desired - all in miniature, t=
o make it comprehensible to readers new to your problem. (It is also not un=
common to discover what a problem actually is in the process of reducing it=
 to an illustrative version.)


USE INFORMATIVE SUBJECT LINES

When posting to the XSL-List, do not use uninformative subject lines like "=
Urgent", "Question", or "Newbie HELP!!!", which don't say anything about wh=
at your problem is. Instead, use a meaningful subject line that will make s=
ense to the people whose help you are trying to get. It may even get a resp=
onse from people who normally shy away from "beginner" questions.

Informative subject lines make the XSL-List archive more useful since peopl=
e with the same problem will more easily find the relevant threads.


DO NOT CROSS-POST

Cross-posting to the XSL-List and to another list, even XML-Dev or the DSSS=
List, is generally counter-productive. No list's archive will contain the c=
omplete thread; cross-posts from non-subscribers continuing the thread will=
 bounce; and XSL-List subscribers who are not also on the other list will o=
nly see half the thread, as will those on the other list who are not also r=
eading XSL- List. Subscribers to both lists may see two copies of the messa=
ge, annoying them as well.


REPLIES GO TO THE LIST

The reply address of XSL-List messages (and of digests) is [email protected]=
ulberrytech.com so REPLIES GO TO THE LIST BY DEFAULT. If you want to reply =
to just the author of a post, you should change the "To:" field in your rep=
ly.


USE SHORT QUOTES OF PREVIOUS MESSAGES IN REPLIES

Please do not quote entire messages just to add a few lines at the beginnin=
g or end. Instead, quote the parts to which you are directly replying or qu=
ote enough to establish the context.

Everybody on the list has already received the message that you are quoting=
, and anyone searching the archive will find your message and the previous =
message listed under the same thread.

Subscribers to the XSL-List will just ignore most of the quoted messages an=
d move to the next post, but subscribers to the XSL-List Digest will mostly=
 have to page past the quoted messages to reach the next material in which =
they are interested in reading.


POSTINGS MUST BE IN PLAIN TEXT ONLY

Postings to XSL-List must be in plain text only. The XSL-List does not allo=
w=20
HTML postings because many users cannot display them appropriately, and bec=
ause=20
they are unnecessarily large.=20


ATTACHMENTS ARE BANNED

Since Mulberry's mailing lists have in the past been unwittingly used for s=
preading viruses in e-mail attachments, all e-mail attachments are banned f=
rom the XSL-List.

XSL stylesheets are XML files, and XML files are text files, so this does n=
ot affect the majority of posts to the list since you can include the files=
' text in the body of your message. If you need to refer to a binary file s=
uch as a PDF file, you should put the file on a Web site or FTP site and in=
clude the file's URL in your XSL-List post.

If you do include an attachment in your XSL-List post -- even a HTML attach=
ment -- your message will bounce.


YOUR POST WILL BE PERMANENTLY ARCHIVED

Because it is a public resource created by and for the entire XSL community=
, we do not edit XSL-List. Therefore, it is responsibility of
list subscribers not to post anything to the list that they do not want pub=
licly available, possibly for a very long time.

Postings in the list archives will be complete, including: all contents, ex=
amples, sample data, code or code fragments, and email header and footer co=
ntents. An automated process will obscure the domain portion of email addre=
sses (the part after the @ sign).in the headers and footers of postings, bu=
t no guarnantee is made that this process will be completely successfull. O=
ther than this, all postings will be archived in public as received.

Further, we at Mulberry could not, even if we wanted to, edit all of the ar=
chives of XSL-List. Several third-parties have created unofficial archives =
of XSL-List, often without asking, or even informing, Mulberry. Postings to=
 XSL-List will be included in an unknown and ever-changing variety of web p=
ublications. If you don't want your questions/comments/answers in public vi=
ew don't post them to XSL-List.=20


THIRD-PARTY ARCHIVES OF XSL-LIST

Third parties are welcome to create searchable or reference archives of XSL=
-List provided they adhere to the following guidelines:=20
- the material is clearly labelled as being from XSL-List, with an acknowle=
dgement of Mulberry's role as provider of XSL-List
- there is a navigable pointer to the official list page at http://www.mulb=
errytech.com/xsl/xsl-list/ either on every posting or associated with the u=
ser interface such that it is visible with the postings
- list postings are unedited
- either the entire archive of the list is provided or there is a clearly s=
tated method for selecting the subset of the list that is provided

Mulberry does not provide these third parties with help to create these arc=
hives, does not endorse particular third party archives, and has no control=
 over the ways in which they present the material in their systems.

People or organizations that publish the contents of XSL-List without follo=
wing the guidelines above are being very antisocial. Please bookmark either=
 the official XSL-List archive or one provided by a service that plays nice=
ly in the community and shun those who do not give credit where credit it d=
ue.


UNSUBSCRIBING FROM THE XSL-LIST

To unsubscribe from XSL-List, use the form at http://www.mulberrytech.com/l=
ists/subscribe-unsubscribe.html or click on the =E2=80=9CEasyUnsubscribe=E2=
=80=9D link at the bottom of any message you receive from the list.=20

If you have difficulties unsubscribing from the list make sure you are unsu=
bscribing EXACTLY the email address that is subscribed.


IF YOU STOP GETTING XSL-LIST MESSAGES

If you stop receiving XSL-List message, you may have been removed because m=
ail to you was bouncing. You are not being picked on, and you can just rejo=
in the list.


ARCHIVE

XSL-List messages are archived at http://www.biglist.com/lists/xsl-list/arc=
hives/.


REPORTING BUGS IN SOFTWARE

Bugs in software should firstly be reported to its author rather than to th=
e XSL List. Questions regarding how to work around bugs are welcome, but th=
e list does not function as a bug-tracking system for any software.


INFORMATION ON XSL

The W3C information on XSL is at http://www.w3.org/Style/XSL.

Mulberry's Quick References are at http://www.mulberrytech.com/quickref/ an=
d cover XSLT, XPath, and XQuery.


DSSSLIST -- THE DSSSL USERS' MAILING LIST

Mulberry Technologies, Inc., also provides the DSSSList -- the DSSSL Users'=
 Mailing List. For subscription information and the DSSSList archive, see h=
ttp://www.mulberrytech.com/dsssl/dssslist.


CONTACT

If you have any questions or problems, please contact xsl-list-service@list=
s.mulberrytech.com.


ADMINISTRATIVE COMMUNICATIONS

The list administrator will reply to emailed questions relating to the mech=
anics and administration of XSL-List and to help new users learn to use the=
 list. However, the administrator will not take the time to navigate mazes =
of any sort in order to do so. If the list owner's messages are rejected by=
 a user's anti-spam system the list owner will not pursue the matter. Simil=
arly, if list-related notices to a subscriber are rejected as spam the subs=
criber will be unsubscribed.=20



CHANGE History


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
November 1, 2017 - btu.=20

14. Changed owner contact address to [email protected]=
m .=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
May 1, 2014 - btu.=20

13. Removed prohibition from sending Base64 messages to the list because I =
think they are compatible with the new list software.=20

12. Modified instructions on subscribing and unsubscribing to the list.


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
December 26, 2011 - btu.=20

11. Clarified instructions on unsubscribing from the digest version of the =
list.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
May 5, 2009 - btu.=20

10. Added paragraph clarifying that all content will be archived in public,=
 including text, examples, code, and email headers and footers including na=
mes.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
February 1, 2008 - btu.=20

9. Policy on third-party archives added.=20

8. Policy banning attachments and postings in Base 64 clarified.=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
September 1, 2007 - btu.=20

7. Administrative communication policy clarified.=20=20


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
October 1, 2005 - btu.=20

6. Mulberry Technologies' relationship to XSL-List clarified. We do the wor=
k. We pay the bills. Organizations who post unauthorized copies of the arch=
ive without acknowledging Mulberry's contribution are not playing nicely in=
 the community.=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
March 2, 2005 - btu.=20

4. Users are asked to identify the version of XSLT and XPath they are using=
 for questions that are specific to one version

5. Clarifying the policy on editing the list archive (we don't edit it).=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
March 30, 2004 - btu.=20

1. All references to subscribing and unsubscribing have been updated to ref=
lect changes in the list management system.

2. Pointers to the XSL and XPath specification were removed. There are now =
so many specifications and draft specifications relevant to XSL that it is =
more practical to simply point to W3C's XSL page.=20

3. A few typographical errors were corrected.
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/3329386
or by email: [email protected]
--~--