← Prev in month
← Prev in thread
Next in thread →
Next in month →
candidates of XML elements
In order to simplify the list of elements as a standard, I think we should choose only important elements from the PSLX standard, and add some elements if necessary. The first candidates would be: $B$H$j$"$($:!"#P#S#L#X$N;EMM$+$i@dBP$J$/$F$O$J$i$J$$%?%0$r(B $B%T%C%/%"%C%W$9$k$H$3$m$+$i$O$8$a$?$$$H;W$$$^$9!#:G=*E*(B $B$K$O!"$"$kDxEY87A*$7!"%7%s%W%k$J$b$N$K$7$?$$$H;W$$$^$9!#(B $B$"$H!"B?>/!"DI2C$b$"$C$F$$$$$H;W$$$^$9!#$D$^$j!"#P#S#L#X$O(B $B#O#A#S#I#S$N3HD%7O$H$$$&7A$K$9$k$H$$0F$G$9!#$^$:!"@dBP(B $BI,MW$J$b$N$O!"(B First, primitive element which are required for fundamental definition of planning and scheduling problems are listed. The meaning of these terms will be described in another mail. <customer> <supplier> <item> <resource> <operation> <order> <lot> <task> <event> The next is a relational element which connects two of primitive elements $B$"$H!"0J22,(B -- Yasu Nissy (Yasuyuki NISHIOKA), Dr.Eng. MIT, 41-211 77 Massachusetts Ave Cambridge MA 02139 Phone 617-452-2982, Fax 617-253-2249 <>
← Prev in month
← Prev in thread
Next in thread →
Next in month →