I have lost sight of the requirements; what is metadata setting out to
achieve that I should evaluate XML as a solution against?
My engineering instinct is always to reuse an existing technology if it is
good enough, not too simple and not too complex for the task in hand. XML
seems to be being c
Hi,
I think there could be benefit to using a strict XML format, but there
are also tradeoffs.
Pro:
Compatibility with other protocols for doing manager-device
communications. The Netconf WG is developing an XML-based approach to
configuring devices; using a format that is compatible with netconf
> 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,
