Just create tags in the form namespace:name. The part before the colon is the namespace name, and allows you to have tag names like "br" without them conflicting with other people's tags named "br", because yours would be named something like mystd:br. Read some books on XML and look into namespaces.
As to the document, if its for your own needs, write it any way that makes sense to you. You just need to define what your tags are and what they mean, how apps should react when they see them, etc... -------------------------- Dean Roddey The Charmed Quark Controller Charmed Quark Software [EMAIL PROTECTED] http://www.charmedquark.com "If it don't have a control port, don't buy it!" ----- Original Message ----- From: "Ravi_Jain" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 03, 2002 9:23 PM Subject: RE: Defining/Assigning meaning to tags ! > thanks Mr Dean for the info > We are not actually in need for real standard > Our requirement is to make some tags meaningful so that we can use them in > our own setup . > can u thro some more light on so as how to go about creating own namespace > and writing the document to assign meaning to the tags ? > > Thanks in Advance > Regards > Ravi Jain > > > > ---------- > > From: Dean Roddey[SMTP:[EMAIL PROTECTED]] > > Reply To: [EMAIL PROTECTED] > > Sent: Friday, January 04, 2002 10:49 > > To: [EMAIL PROTECTED] > > Subject: Re: Defining/Assigning meaning to tags ! > > > > Anyone can define their own XML tags, and define any standard > > functionality > > that they believe those tags should cause. The easiest way to do this is > > to > > put your own tags into a namespace of your own, like "mynamespace:mytag", > > where mynamespace is related to your company or the standard you want to > > create. Then write up the document that indicates what each tag means and > > how applications should react to them. > > > > If you actually want it to become a real standard, then that's a whole > > different story. You'd have to either get the backing of some consortium, > > such as the W3C, or push it yourself until it gets accepted. Either one is > > probably pretty hard. > > > > -------------------------- > > Dean Roddey > > The Charmed Quark Controller > > Charmed Quark Software > > [EMAIL PROTECTED] > > http://www.charmedquark.com > > > > "If it don't have a control port, don't buy it!" > > > > > > ----- Original Message ----- > > From: "Ravi_Jain" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Thursday, January 03, 2002 9:10 PM > > Subject: Defining/Assigning meaning to tags ! > > > > > > > Hi All > > > I want to define(design) some tags for standardisation. > > > for example as in case of HTML tags .."<br>" is understood as break > > point > > > etc.. can anyone let me know if similar functionality is possible with > > XML > > > ...so that I can define my tags to understand what to do with its > > argument. > > > Thanks in Advance > > > Regards > > > Ravi Jain > > > > > > > > > > > ************************************************************************** > > > This email (including any attachments) is intended for the sole use of > > the > > > intended recipient/s and may contain material that is CONFIDENTIAL AND > > > PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying > > or > > > distribution or forwarding of any or all of the contents in this message > > is > > > STRICTLY PROHIBITED. If you are not the intended recipient, please > > contact > > > the sender by email and delete all copies; your cooperation in this > > regard > > > is appreciated. > > > > > ************************************************************************** > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > ************************************************************************** > This email (including any attachments) is intended for the sole use of the > intended recipient/s and may contain material that is CONFIDENTIAL AND > PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or > distribution or forwarding of any or all of the contents in this message is > STRICTLY PROHIBITED. If you are not the intended recipient, please contact > the sender by email and delete all copies; your cooperation in this regard > is appreciated. > ************************************************************************** > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
