Re: [egov] Re: [huml] The Office of Justice Programs's (OJP) Justice XML Data Dictionay

[Duane Nickull <duane@yellowdragonsoft.com>]

David / Rex et al:

Thanks for the CC.

What you both suggest is certainly feasible given the existing OASIS 
Registry specs (well the ebXML one anyways - I am not sure you could 
accomplish this in a UDDI registry).  RDF schemes to classify sets of 
registry content is something that will likely be done.  IMO - it may be 
akin to creating an extra layer however (unless I have somehow missed 
some of this thread which I suspect may be true).  Since RDF is itself a 
classification scheme, having the Registry classification scheme point 
at an RDF set first, which in turn points at a the actual registry 
objects, may be overkill but hey - what do I know.

Using RDF as a classification "Guide" may be interesting and there may 
be a specific use case for it however there may be a dependency on XML 
itself.  The built in registry classification mechanism may be more 
flexible in terms of accounting for non-XML syntax (UML).

David has been working on an important part of aggregation called CAM 
(Content Assembly Mechanism).  CAM would function like a schema template 
whereby a user could declare the context it would be used in, then a 
search of the registry would yield the appropriate artifacts to populate 
the final schema instance with (assuming XML was the end syntax - other 
end syntaxes may also be possible).

CAM has an important role is providing a meta-description of payload 
level aggregations.  XML Schema may be useful as an expression of CAM 
but RDF may alos be useful.  I guess we'll have to wait for the final 
draft to see what can be used.  I have a sneaking suspicion that RDF may 
lack the necessary cardinality (multiplicity) operators for advanced 
representation of metadata.

Yellow Dragon Software hopes ot be able to offer our registry product 
for download from our website sometime within the next 3-4 weeks.  I 
would invite people to download an evaluation copy and test some of 
these scenarios out and share their experiences with us all.

Interesting conversation.  enjoy!!

Duane Nickull
-- 
Yellow Dragon Software - http://www.yellowdragonsoft.com
Service Oriented Architecture Components - ebXML, Web Services, SOAP
Project Team lead - United Nations CEFACT eBusiness Architecture
+1 (604) 726-3329
***********************************


Rex Brooks wrote:
> 
> David,
> h
> We're agreed.
> 
> I took the liberty of including you and Duane on the list for another 
> posting related to this discussion. I look forward to hearing what Duane 
> thinks.
> 
> Ciao,
> Rex
> 
> At 10:13 AM -0400 5/17/03, David RR Webber - XML ebusiness wrote:
> 
>> Rex,
>>
>> OK - we're on the same pages here!
>>
>> BTW - I think you should look at how storing RDFs into an OASIS Registry,
>> using the classification scheme approach that OASIS provides, and
>> then creating searches against that RDF could provide you with
>> semantic cross-referencing.
>>
>> You can also manually setup associations across content, both
>> internally and externally using the registry.
>>
>> I've CC:d Duane Nickull who can followup with you offline on these
>> ideas to see how this might work.
>>
>> Always good when we can tie the work of multiple OASIS TC's
>> together to produce the required solution.
>>
>> Cheers, DW.
>> ================================================================
>> Message text written by Rex Brooks
>>
>>>
>> What I am thinking now is how a tool that produces the kind of
>> registry you describe would be very useful when applied to resources
>> from an rdf schema that accompanies a given specfication, for those
>> resources that can be used by such a tool, to produce quick
>> comparisons from which an application developer could choose the best
>> set for a given application.
>>
>> <
> 
> 
> 


-- 
Yellow Dragon Software - http://www.yellowdragonsoft.com
Service Oriented Architecture Components - ebXML, Web Services, SOAP
Project Team lead - United Nations CEFACT eBusiness Architecture
+1 (604) 726-3329
***********************************