Re: [ubl-ttsc] Minutes of 20 November meeting

[Anne Hendry <anne.hendry@sun.com>]

Hi Chee-Kai,

Sorry for the delay in response.   See below.

>>>  It would be useful to show a cooperative tools environment - how users
>>>  can put together existing tools and technologies to develop with UBL.
>>>  Something to provide a guideline for developers and gives them some
>>>  idea of what directions we think tools will go.
>>>      
>>>
>
>This is an interesting idea - a cooperative tools environment.
>Is there elaboration on this?
>  
>
We didn't get in to much detail on this in the last call.
However, the idea is that we have multiple tools (and this is bound to 
continue to be the case)
which have variouis degrees of overlap.  One value we could provide to 
UBL developers is to
help them through the maze of tools by giving them guidelines on useful 
tools features as we
have found them in our development, and as others have found them 
through use (this latter
type of information would come very likely through the Implementation 
SC, so we need
to keep a tight connection with that team).  Taking this further would 
produce information
on how the various existing tools can be used together to provide the 
needed functionality.
Perhaps a table of features of each tool, which provides what, where 
they integrate easilty.

I'm sure others can expand in their own way on what this means to them,
and I see more of this discussion coming out of the review and further 
development
of Chris's paper, as part of a tools overview documenation deliverable 
perhaps.

Thanks for your elaborations below of UBLish functionality/use.
I'd like to discuss this further over the following week in relationship 
to the purpose,
user, and functionality goals outlined in Chris's paper.

Thanks,
Anne

>>>  We need a document that describes the current process - how you can
>>>  change a spreadsheet/model and use ublish to create new schemas and
>>>  be close to ccts compliance.  Is this doable with out incurring any
>>>  additional cost?
>>>      
>>>
>
>UBLish was more an "internal" tool that was originally designed to 
>bring out UBL deliverable schemas than to be an end-user commercial 
>tool.  Yet, the feedback I heard so far appears that that's exactly
>the kind of modeling/transformation process that users are 
>looking at.  
>
>I understand a couple of individuals and organizations,  for 
>instance, have used UBLish (0p70) to transform the modified
>spreadsheets to produce their own schemas.  That appears to be
>the most straightforward, painless and relatively reliable way
>to get a "nearby" schema around UBL's.  
>
>The steps would just simply be to pick one of the spreadsheets
>and start modifying its contents in a way that addresses 
>one's data modelling needs.
>
>The more ambitious ones who picks up a bit of XPS programming
>might start working into the UBLish internals to look at things 
>to modify.   But of course, there's a chance that if one modifies 
>the wrong thing, one might end up getting VBL-lookalike schemas
>instead....
>
>
>
>
>  
>
>>>  This description is needed from the modeling side
>>>  - to show how you can use uml to create the schemas.  The problem
>>>  is that there is no way from the UML at the moment to know that
>>>  the BIEs being used are already in existence.  There is no tool
>>>  at the moment that can do this.  So quite a bit of the development
>>>  would be manual.
>>>      
>>>
>
>The UBLish "detects" this during schema generation process
>by proceeding through with the schema generation, but tagging
>the offending type usage line with an "Error" comment block.
>As the erraneously typed lines would have prefixes "unknown:"
>without namespace definition, the resulting schema would cause 
>schema validators to fault, allowing users to be notified of
>problems and retrospectively correct them at the spreadsheet
>sources.
>
>So the end goal for the end-user in customizing his/her own
>schemas would then be to look through the generated schema
>and find zero "Error" comment block.
>
>This refinement process was also exactly the steps that 
>Library Content side went through in a multi-party iterative
>process to generate the UBL schemas.
>
>
>
>
>
>Best Regards,
>Chin Chee-Kai
>SoftML
>Tel: +65-6820-2979
>Fax: +65-6743-7875
>Email: cheekai@SoftML.Net
>http://SoftML.Net/
>
>
>
>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/ubl-ttsc/members/leave_workgroup.php.
>
>  
>