Lists Home |
Date Index |
Oh yes - RDF is a different animal indeed!
However - CAM <ContentReferences> do this mix-n-match for you very
neatly without incurring the overhead of RDF - very simply using an
Alias mechanism. So you can create an Alias that points to a particular
registry domain - eg : USPS - Addressing registry run do US Postal, and
say OAGi - ERP system registry run by Open Application Group. Now you
simply associate the correct definition to the domain registry. And
include structure components into your XML transaction accordingly.
Unlike namespaces these registries are 'live' and can actual return you
noun definitions and more - that can be used by processors such as jCAM.
Or of course - you can simply 'consume' the semantic facts in the CAM
template 'as is' and use this to do reasoning - crosswalking - etc, on
your own in your own software components.
Alaric Snell-Pym wrote:
> firstname.lastname@example.org wrote:
> [pet namespace peeve]
>> In 99% of cases the natural XML heirarchy and XPath are enough:
>> <amount value='21343.23'/>
>> <postage><amount type='postage'>12.50</amount></postage>
> That depends on what you're doing; RDF folks have a usage pattern that
> (legitimately IMHO) brings together a few elements each from lots of
> different namespaces: