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

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: hey whilst we are all asking for things

Hi Dean,

There is a very large vocabulary you can get at :
http://www.openapplications.org/downloads/oagidownloads.htm

This vocabulary has 190 messages, 60 objects, and hundreds of core
components.  It is also based on UN/CEFACT CC and is committed to
contribute
and adopt moving forward.



-----Original Message-----
From: J. Dean E. P. Hemopo [mailto:jdeanh@ihug.co.nz] 
Sent: Tuesday, July 13, 2004 4:07 AM
To: ebXML Dev Forum
Subject: hey whilst we are all asking for things

hello all,

i have just started digging into a big helping of UBL.  all good so far.
it
became apparent that there is a great source of CCTS (Core Component
Technical Specification:  see ebXML), i should say Core Component, stuff
here.  i am yet to gather appropriate material for the "Data-Dictionary",
and think some good sources are in UBL.   but i want/NEED more of the
same,
qualifiers, representation term, root terms,  and alike.  yes i have the
EDIFACT dictionairies, do i have to chop that up?  is there another source
of rudimentary business vocabulary.

will UBL be sufficient for a prototype.

another question is, i was perving through UBL, looking at the
spreadsheets
for just such data, and noticed that some elements had an underscore
prefix
( "_").  what does that mean.

also, i had the answer but cant find the source any more, when you have a
qualifier->root term qualifier->root term, relationship (like customer.
account. number), i notice they have the term name, followed immediately
by
a period, a space and then the next term, period, and so on.  now i know
that is the presecribed depiction, what is the source for that
specification. (ISO-11179 ?:)

and if i have not asked for enough  for one session, whats with that gap
before a period, do we have to parse this "space" char and stuff out of
the
model, depending on your processing requirements (as per application) to
deal with it.  what did he just ask?

ok, i have "customer. account. number", now that is meaningful to others
who
know the spec, and how to use it.  but besdides its semantic meaning, it
is
useless like that.  so i chop it up, parse it, extract out
customeraccountnumber, and see if i have that in my repository.  well i
dont
know about you, but thats what i am thinking of doing, or should i leave
it
like that and look for exact matches on the original space delimited
string
"customer. account. number".  whats with the "space" charactor between it
all anyhow?  just convention ?

thanks for your answers in advance.

dean hemopo
auckland, new zealand



The ebxml-dev list is sponsored by OASIS <http://www.oasis-open.org> The
list archives are at http://lists.ebxml.org/archives/ebxml-dev/
To subscribe or unsubscribe from this list use the subscription manager: 
<http://www.oasis-open.org/mlmanage/>




The ebxml-dev list is sponsored by OASIS <http://www.oasis-open.org> The
list archives are at http://lists.ebxml.org/archives/ebxml-dev/
To subscribe or unsubscribe from this list use the subscription manager: 
<http://www.oasis-open.org/mlmanage/>

<<attachment: winmail.dat>>



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