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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-dev message

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


Subject: Re: [ubl-dev] Text Type – Unspecialised and Text Type - Core Component Types


Hi Fraser

A Core Component Type (CCT) is more 'abstract' in that it is not used
in messages directly. Rather it can be used in two ways:
1) as a basis for the Unspecialized Datatype (UDT)
- typically using 'xsd:base' when such types are defined in XML with XSD
Schema
2) as a datatype component of a Basic Core Component (BCC)

Similarly, Basic Core Components built with Core Component Types
are not used in messages but rather Basic Business Information Entities
(BBIEs)
are modelled on them (though not in this case 'based' on them using
'xsd:base'), possibly specializing them, and these BBIEs are used in the
messages.
The BBIE modelled on a BCC uses datatypes which correspond to the respective
CCTs of the underlying BCC. Each datatype would either be the same type as
the
CCT (such as Text) or would be a specialized form (such as Name). It now
gets
a little confusing though (if you weren't confused already :-) ) in that it
seems an
'Unspecialized Datatype' can be a specialization of the CCT (as with Name
being
a specialization of the Text CCT) but in some cases the UDT is not a
specialization
(such as the Text UDT which is more closely equivalent to the Text CCT).
This is
really a matter of terminology causing the confusion. In ATG2 the UDTs are
called
Unqualified Datatypes which might be less confusing. There is the
possibility of
a group of modellers further specializing (or further 'qualifying', in ATG2
terminology) the UDT to make a Specialized datatype (SDT) (or 'Qualified
Datatype'
to use the ATG2 schemas term).

** Now, in short, the BBIEs can use either UDTs or SDTs but not directly use
CCTs. **

The Name UDT doesn't have to specialize the structure of the Text UDT. Both
have the
same structure in UBL (string content with just a single attribute for
language). The
specialization seems to be one of function rather than structure. In UBL
though the
Text UDT is a restriction of the Text CCT and I'm not sure why this is. The
Text CCT
has an attribute for 'language' an extra attribute for 'languageLocalID'
whereas the UBL
Text UDT (and the UBL Name UDT) have just the 'language' attribute.

Sorry if I haven't really answered your question. Perhaps my answer is dumb
but I don't
think your question is :-)

All the best

Stephen Green



----- Original Message ----- 
From: "Fraser Crichton" <fraser.crichton@solnetsolutions.co.nz>
To: <ubl-dev@lists.oasis-open.org>
Sent: Thursday, June 16, 2005 3:53 AM
Subject: [ubl-dev] Text Type – Unspecialised and Text Type - Core Component
Types


> Hi,
>
> I'm trying to get more familiar with UBL and with some of the concepts
> behind it's use.
>
> I was just wondering about the reasons behind declaring TextType – as an
> Unspecialised type and TextType as a Core Component Type and in
> particular when you would use one over the other?
>
> Hope this isn't too dumb a question but I'm trying to understand more of
> the methodology behind UBL as well as how I would apply it.
>
> Cheers,
>
> Fraser
>
>
> Attention:
> This email may contain information intended for the sole use of
> the original recipient. Please respect this when sharing or
> disclosing this email's contents with any third party. If you
> believe you have received this email in error, please delete it
> and notify the sender or postmaster@solnetsolutions.co.nz as
> soon as possible. The content of this email does not necessarily
> reflect the views of SolNet Solutions Ltd.
>
>



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