Re: Comments on the HR Draft

[Derek Neighbors]

Todd,

Just like ebXML and ALL other standards GNUe can/will conform.  When I say 
this GNUe is not a shrinkwrapped fixed thing.  If there are elements 
missing that need to be there for some spec one can easily add them, as 
for 'formatting'.  I think datastorage via xml is a bad idea, but we 
already today in (reporter) and later in integrator will have means to set 
a fixed mapping output to virtually anything, including XML.

So if all the data is 'there' it would be a matter of mapping it out (one 
time) and then you coudl export to HR-XML and have the data pushed around 
to other systems supporting HR-XML.

I hope that makes sense.

Derek

 On Tue, 11 Dec 2001, Todd Boyle wrote:

> Would somebody kindly report on any relationship between the HR proposal
> and HR XML?  Will GNUE HR interfaces or data model converge with hr-xml
> information structures?
> 
> Their page is at http://www.hr-xml.org/channels/home.htm
> Their list archives are at http://lists.hr-xml.org/archives/
> 
> Chuck Allen, the leader of HR XML is a good player.  He did good work
> as master of ceremonies at the OMG Interop last week.  That was attended
> by approx. 100 people from numerous standards bodies working to converge
> and coordinate and harmonize the work they are all doing. The presenters
> promised to upload their powerpoints from the meeting in coming days, at
> http://www.omg.org/interop
> 
> Anyway-- I apologize if this has already been answered but, in general,
> I remain very interested in GNUE's compatibility with global standards
> for e-business, either at the interface or at the core,
> 
> Respectfully
> Todd Boyle CPA
> www.arapXML.net
> www.gldialtone.com  etc,
> 
> 
> At 10:06 AM 12/11/01, Derek Neighbors wrote:
> >I made some 'grammatical' comments in IRC to neilt about the HR proposal
> >that he was going to incorporate, since he is not around today in irc, I
> >figure will make the technical ones via email.... :)
> >
> >All comments are about section 2.1.7 Business Object Definitions...
> >
> >class hire: (i dont know if this is the best name for this class)
> >all xxxxx_codes should really be codes that point to lookup classes like
> >status.  About what about people that come back, this is good question, I 
> >think
> >we might want a rehire date or break the hiring portion out so it can
> >be 'revolving thing'.
> >
> >class contract:
> >I keep seeing reference to 'posts' what is this?  Like title? Postion?...
> >As far as contract details and jobcode/title there is a LOT more to it,
> >but I think maybe that is teh posts module?
> >
> >class former_emp:
> >Since you are capturing this data, do you want to include pay information
> >from last job?  And would you limit this to a single former employer?  or
> >during the hire process would you catalog all the data during reference
> >checking?  If so would you want to list who you talked to at that company
> >and when and what they had to say about the employee. (i realize that this
> >might be a separate module like 'recruiting' or something)  Just throwing
> >out the idea...
> >
> >** note on things like relationship/status etc... It might be better to
> >list them after the class that uses them, because I thought wtf are these
> >sitting out here all alone for, until I saw them referenced in another
> >class.  That or make better comments for them. :)
> >
> >
> >Derek Neighbors
> >GNU Enterprise
> >
> >
> >_______________________________________________
> >Gnue mailing list
> >address@hidden
> >http://mail.gnu.org/mailman/listinfo/gnue
> 
> 
> _______________________________________________
> Gnue mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/gnue
>