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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-regrep message

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


Subject: FW: ebXML-BP Website Status & Proposal


hey RegRep team!  
do we have a WIP (i.e., more private) area of the Reg/Rep web pages on
ebxml.org?  along with doing a complete data update of the Reg/Reg Team
pages, i would like to see a "public" and  "wip" area similar to what brian
has documented for the BP site.  i strongly agree with brian that we
standardize on the look-and-feel of the public pages with the rest of the
web site.  any comments and questions would be welcome.
joel munter


-----Original Message-----
From: Hayes, Brian [mailto:Brian.Hayes@Commerceone.com]
Sent: Friday, September 22, 2000 2:02 PM
To: 'ebXML-BP@lists.ebxml.org'
Subject: ebXML-BP Website Status & Proposal


  I found a version of our old work-in-progress web site (on my home PC) and
Karl Best has posted the recovered files.  I posted most of my home PC
version this morning and it can be found at
http://www.ebxml.org/project_teams/business_process/wip.  I did not check
it; so, some of the links may be broken.

Here's my proposal for our web site, which we will review on 25 September
teleconference:
   The web site logically divides into "public" and "work-in-progress", with
corresponding subdirectories "pub" and "wip" (pub is short for "public
house" which is a place we should visit for a pint after submitting a
document for public review; wip is short for "wipped" which is how we feel
after we've spent those long hours working on documents).
   Under pub and wip we directories for each of the efforts and subteams.
For example, metamodel, methodology, and core-process.  I figure we don't
need to put the core-process team directory under the methodology directory.
   So, the overall structure, in outline format, looks like this:
project_teams/business_process/
+ index.html (replaces business_process.htm)
+ images/
+ pub/
	+ index.html
	+ faq.html
	resources/ -- e.g. TMWGN090, plus a page with links to other
resources
	metamodel/
	methodology/
	coreprocess/
	etc...
+ wip/
	+ index.html
	resources/ 
	metamodel/
	methodology/
	coreprocess/
	etc...

   Just to make things more fun, XML will be used to create some of the data
on the web pages.  For example, the resources page and FAQ page can be
represented in XML and then transformed using XSLT.
  
   For the work-in-progress section I am not planning to use the standard
ebXML look since it  is a complicated HTML structure.  I want to make it
easy for folks to create web pages.
   I will also make use of CCS (Cascading Style Sheets).  Specifically,
there will be a bp.css sheet in the business_process directory.  We'll
modifiy it untill it looks acceptable.
---

Let me know if this is okay with you.

Brian





[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