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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-core message

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


Subject: Re: ISO 8601 anyone?? And more on Parties.


It's clear Ian Galpin really, really likes ISO 8601, and wants the rest
of us to use it everywhere, not just in the XML instances of core
components. I'm sympathetic - but it does take a lot of conditioning for
those Americans to start doing it right.  Most people do want to follow
standards if they're easy to understand;  it helps that XML Schema
includes a datatype for dateTime which enforces the ISO 8601 extended
format CCYY-MM-DDThh:mm:ss.  And it would be a really rare case where we
would have to break out the individual year, month, day, hour minute and
second, as Brian Hayes demonstrated.

It should please Ian to know that no one is fighting a standard DateTime
format, though it's still not clear Core Components "gets it" with
respect to the date time.type in the catalog - it STILL has a date
time.format.text code which is defined as "[Using] values from ISO
8601," whatever that means - there are no "format text codes" in ISO
8601.  Hopefully, we'll eventually end up with some core component,
manifested as an ISO 8601 extended format, which everyone feels
compelled to adopt - including RosettaNet which now uses the non
schema-compliant basic format without the dashes, e.g.,
20001121T145200.000Z.

But ebXML Core Components really needs a lot more than just a dateTime
component.  It's still struggling to get a Party core component off the
ground!  And in the meantime, because CC couldn't come up with one, TR&P
and the Trading Partner groups had to devise their own based on URIs
using domain names (which don't  exist, yet!) - for example:

        <eb:PartyId type="urn:duns">123456789</eb:PartyId>.

Is CC going to change their party.identifier to be consistent with the
way the TR&P messaging services and the CPP use it -  based on URIs?

William J. Kammerer
FORESIGHT Corp.
4950 Blazer Pkwy.
Dublin, OH USA 43017-3305
+1 614 791-1600

Visit FORESIGHT Corp. at http://www.foresightcorp.com/
"accelerating time-to-trade"




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

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC