OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep-semantic message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [Fwd: Re: [cam] Groups - CAM AND REGISTRY ACCESS.doc uploaded]


Team,

FYI here - Martin has adapted the original noun XSD I originally posted 
here and made it work
with CAM.

In the next couple of weeks we will have the jCAM implementation in 
testing with this and be
able to share that so we can try it with some business examples.

I'm seeing that the UK Gov Registry work can look at this - and also the 
Canadian Gov to
see how well this new revised structure fits their use cases.

That should allow us then to refine everything - and then ultimately 
post a complete noun XSD
here and the associated approach.

Thoughts, comments and feedback gratefully received!

Thanks, DW

======= Forwarded message ===========
Martin,

This I believe is truely ground breaking stuff you have enabled here.

Basically what this all enables is storing rules in a registry about your
vocabulary and dictionary items - and then being able to have jCAM
automatically retrieve those and apply them to your XML transaction
with only minimal coding in the actual CAM template itself.

The way we had it before - you had to manually associate everything
thru the content reference section.  This new approach IMHO is way
easier and much more powerful.   It also accommodates those people
who wish to use XSD fragments to augment their CAM predicate rules.

I also like how easy it is to generate these fact sets from an existing
dictionary database - just by dumping out XML from the SQL and
applying some production rules to get the CAM predicate syntax.
I suspect UBL, OAGi and others will be able to quickly generate
default rules sets using this approach.

As we get more and more of this working in jCAM - the more we
are able to validate the CAM approach.

I look forward to seeing how this matures and getting everyones
feedback on how well this plays out for them.

Thanks, DW
============================================
martin.me.roberts@bt.com wrote:

> The document CAM AND REGISTRY ACCESS.doc has been submitted by Martin 
> Roberts (martin.me.roberts@bt.com) to the OASIS Content Assembly 
> Mechanism TC document repository.
>
> Document Description:
> The purpose of this document is to provide a review the current 
> content reference section processing in the CAM template specification 
> and to clarify and update the details to accommodate the latest work 
> by other OASIS teams such as the Registry TC.  Also included are 
> recommendations that resolve inconsistencies and omissions from the 
> existing specification details.
>
> Download Document:  
> http://www.oasis-open.org/apps/org/workgroup/cam/download.php/9689/CAM%20AND%20REGISTRY%20ACCESS.doc 
>
>
> View Document Details:
> http://www.oasis-open.org/apps/org/workgroup/cam/document.php?document_id=9689 
>
>
>
> PLEASE NOTE:  If the above links do not work for you, your email 
> application
> may be breaking the link into two pieces.  You may be able to copy and 
> paste
> the entire link address into the address field of your web browser.
>
>
>
> To unsubscribe from this mailing list (and be removed from the roster 
> of the OASIS TC), go to 
> http://www.oasis-open.org/apps/org/workgroup/cam/members/leave_workgroup.php. 
>
>
>  
>



To unsubscribe from this mailing list (and be removed from the roster of 
the OASIS TC), go to 
http://www.oasis-open.org/apps/org/workgroup/cam/members/leave_workgroup.php. 


--- Begin Message ---
Martin,

This I believe is truely ground breaking stuff you have enabled here.

Basically what this all enables is storing rules in a registry about your
vocabulary and dictionary items - and then being able to have jCAM
automatically retrieve those and apply them to your XML transaction
with only minimal coding in the actual CAM template itself.

The way we had it before - you had to manually associate everything
thru the content reference section.  This new approach IMHO is way
easier and much more powerful.   It also accommodates those people
who wish to use XSD fragments to augment their CAM predicate rules.

I also like how easy it is to generate these fact sets from an existing
dictionary database - just by dumping out XML from the SQL and
applying some production rules to get the CAM predicate syntax.
I suspect UBL, OAGi and others will be able to quickly generate
default rules sets using this approach.

As we get more and more of this working in jCAM - the more we
are able to validate the CAM approach.

I look forward to seeing how this matures and getting everyones
feedback on how well this plays out for them.

Thanks, DW
============================================
martin.me.roberts@bt.com wrote:

>The document CAM AND REGISTRY ACCESS.doc has been submitted by Martin Roberts (martin.me.roberts@bt.com) to the OASIS Content Assembly Mechanism TC document repository.
>
>Document Description:
>The purpose of this document is to provide a review the current content reference section processing in the CAM template specification and to clarify and update the details to accommodate the latest work by other OASIS teams such as the Registry TC.  Also included are recommendations that resolve inconsistencies and omissions from the existing specification details.
>
>Download Document:  
>http://www.oasis-open.org/apps/org/workgroup/cam/download.php/9689/CAM%20AND%20REGISTRY%20ACCESS.doc
>
>View Document Details:
>http://www.oasis-open.org/apps/org/workgroup/cam/document.php?document_id=9689
>
>
>PLEASE NOTE:  If the above links do not work for you, your email application
>may be breaking the link into two pieces.  You may be able to copy and paste
>the entire link address into the address field of your web browser.
>
>
>
>To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/cam/members/leave_workgroup.php.
>
>  
>



To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/cam/members/leave_workgroup.php.

--- End Message ---


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]