+(44) 192 575 3018
-Original Message-
From: Chris Lonvick <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: 14 January 2004 16:46
Subject: Thoughts on Meta-Data
>Hi Folks,
>
>(Just stirring the pot; please respond and keep this discussion going. :)
>
erasys Networks
> -Original Message-
> From: Chris Lonvick [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 14, 2004 7:54 AM
> To: [EMAIL PROTECTED]
> Subject: Thoughts on Meta-Data
>
> Hi Folks,
>
> (Just stirring the pot; please respond and keep this
> dis
> Below some thoughts...
>
> > Use strict XML such as:
> >
> >
> > Use loose rules so the information can be easily converted to
> > XML (if one wishes) such as:
> >
> >
> > Define the format and delimiters with little regard to any
> > conversion to XML, such as:
> > [cookie msgno=123 enc
Thanks for the ideas Anton,
I'm happy with using the word cookie. It works for me. :-)
To me, there doesn't seem to be a good reason to lean towards using XML
or pseudo XML. I would prefer to avoid any possibility of nested tags
etc. We could use [] or <> for tagging, just something to show open
Below some thoughts...
> Use strict XML such as:
>
>
> Use loose rules so the information can be easily converted to
> XML (if one wishes) such as:
>
>
> Define the format and delimiters with little regard to any
> conversion to XML, such as:
> [cookie msgno=123 encoding=USASCII]
My pref
Resend, as there apparently where some server issues...
Below some thoughts...
> Use strict XML such as:
>
>
> Use loose rules so the information can be easily converted to
> XML (if one wishes) such as:
>
>
> Define the format and delimiters with little regard to any
> conversion to XML,
Hi Folks,
(Just stirring the pot; please respond and keep this discussion going. :)
I've seen the following proposals for the Meta-Data field:
Use strict XML such as:
Use loose rules so the information can be easily converted to XML (if
one wishes) such as:
Define the format and delimit
