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


Help: OASIS Mailing Lists Help | MarkMail Help

ubl message

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

Subject: Re: [ubl] questions about UBL spreadsheets

Dear UBL-TC,

I'm sorry that I sent unreadable e-mail,
because my MTU missed the resolusion of LF code
when it was chainging encoding.

The content is following;
JPLSC is going to hold study meeting of UBL.
And now I'm researching UBL and CCTS specifications for the
purpose of preparing the study meeting.

While researching these specifications, I had some questions and
unclear point about UBL spreadsheets.

If you have any idea about these questions, please tell me.

Q1. How shall we give UBL Name (Column A) to every component?
Does UBL Name have naming rules like Dictionary Entry Name?

Q2. In Core Component Types' spreadsheet, some of supplementary
components have Object Class (Column D) different from  their
owner's one.

In my CCTS understanding, Object Class Terms of properties are usually
same as their owner's one.
I think core component types are special case, and it is a measure to
fit in CCTS's Core Component Type definition.
Is it right?

Q3. In Core Component Types' spreadsheet, every CCT has string "Type"
in their Property Term (Column H). I think that this string "Type" is
for concatenating to Object Class (Column D) to create Dictionary
Entry Name (Column B), because Dictionary Entry Names for properties
are created in such a way.
Is it right?

If it is right, I think the string "Type" might be needed both Data
Type's spreadsheet and string "Details" might be needed the other
BIEs' spreadsheet.

Q4. In Core Component Types' spreadsheet, every CCT's parameter has
value (e.g. Content, Identifier, Text...) in their Representation Term
(Column I).

I can't understand what this column means because CCT's XSD have no
information about these representation terms and there are primitive
type definitions at Column K.

What do these Representation Terms mean?

Q5. In Core Component Types' spreadsheet, every CCT's parameter has
XML Schema's built-in datatypes in Data Type (Column K).
I think you assigned these datatypes to CCTS's primitive datatypes.
Are there some rules for these assignments?

Q6. In Core Component Types' spreadsheet, all of properties have
notation "Supplementary" at Component Type (Column G).
In my CCTS understanding, I wonder if the properties that Property
Term is "Content" might have "Content" at Component Type.

Q7. I'd like to confirm the relationship among the Data Types
definitions & CCT definition.
I think the Data Type (Column K) is the Dictionary Entry Name of
corresponding CCT for UDT and is the Dictionary Entry Name of
corresponding UDT for SDT.

And I also think such correspondences is usually expressed with XML
Schema's "restriction". But the Codes in SDT are special cases that
we can't express with "restriction".

Is it right?

Q8. In every ABIE spreadsheet, every ASBIE property's Property Term
is fixed as Associated Object Class (Column M). It seems more
restricted rule than CCTS's one.
Is it an UBL rule?

I'm afraid that these preceding questions might be trivial or basic ones
for you, and some of them might be defined in UBL specification, though I
have checked it.

Thank you,

Shin Takagi
Hitachi Systems & Services, Ltd.
4-11-4, Omorikita, Ota-ku,
Tokyo, 143-8545 Japan
Tel:+81-3-3763-5403   Fax:+81-3-3763-0469

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