exchange network message board

More information on the NGN

ian — Wed, 02 Jul 2008 20:42:29 GMT

I'm interested in getting a copy of the latest and greatest Next Generation Node from CSC to kick the tires on.

The best I've found is here and the latest is from April 2008. This seems a little dated in the fast moving world of 2.0.

https://test.epacdxnode.net/ngn/

Anyone have another link or a contact at CSC they wouldn't mind sharing?

Thanks!
Ian

Forum: General Node Forum

Any "Next Generation Node" users out there?

jecuhaciyan — Tue, 27 May 2008 22:32:34 GMT

Just wondering who else might be using the NGN out there. We've hit a little bit of a road block with getting it configured and I'm wondering what solutions others have found.

To be more specific, the following is a snippet of the error I get when using the admin tool:

javax.servlet.ServletException: RMI lookup for service failed; nested exception is java.rmi.NotBoundException: cdx-core2/DataflowService

Any ideas?

Thanks!
Jennifer

Forum: General Node Forum

Transfer lab data to agency

GeraldSchwandt — Thur, 22 May 2008 15:04:22 GMT

Are there any standards (schemas, dtds) for transferring analytical results from labs to state agencies? Any one with experience in this area?

Forum: General Discussion Forum

Node 2.0 Rev .8 Questions

jacorob — Wed, 10 Oct 2007 18:50:44 GMT

I noticed that the newest version of the Node 2.0 specs (.8) have been made available through the EN website! I thought it might be appropriate to start a new thread in this forum that is dedicated to the new revision. See http://www.websitetoolbox.com/tool/post/exnet/vpost?id=1861037 for comments on the old one (v .7).

I have a couple initial questions on the .8 specs.

1. When are comments due on this new version? I'm on vacation all next week (out of state) so may not be able to participate in the conference call on Oct 18. Will comments be accepted after Oct 18 or do I need to get them in before I leave?

2. Are there any specific topics or areas of the specifications for which comments are specifically requested?

3. Are there any preferences for how the comments are provided? Should I just attach a word document to a message board post, provide comments inline within a post, email them to the node2.0@exchangenetwork.net email account, etc?

Thanks!

Forum: General Discussion Forum

partners

steve — Wed, 10 Oct 2007 07:24:12 GMT

From reference to the partner profiles page, there seems to be a lack of private partners here.

I was wondering I there is any restrictions for this.

Steve

Forum: Network Project Ideas - Share your ideas and find project partners.

NetDMR Enhancement - FY08 Exchange Network Grant Proposal

bharris — Mon, 01 Oct 2007 13:50:17 GMT

I would like to solicit a lead to develop a challenge/collaboration proposal that might assistfunding NetDMR enhancements beyond Fall 2008 (expiration of the existing grant). Many of you have been a part of the current steering committee or active in the NetDMR development process. If you know of others that may be interested in leading a proposal/project, please forward this note. Some of the suggested activities from the grant solicitation include:1) Pilot testing and launching the NetDMR system within an authorized state via EPA's centrally-hosted system; 2) adaptation of NetDMR to work in a state environment (state hosting), and 3) enhancements to NetDMR - proposed additional functionality that was not designed into Version 1.

Texas CEQ will be able to participate in the proposal/project, but will be unableto lead the effort. We can provide all the information (work plan, etc) from the EN challenge grant that is funding the current project. EPA has been unable to commit to maintenance/enhancement activities at this time since their budget is not final,creating the need for a project like this. Proposals are due Nov. 19, so if this type of collaborative effort if going to happen, we would need a champion/lead now to organize the effort. I thank you for "listening".

Brandon Harris
Texas Commission on Environmental Quality
Manager, Information Strategic Planning
(512) 239-4535
bharris@tceq.state.tx.us

Forum: Network Project Ideas - Share your ideas and find project partners.

Decompress Binary Attachments

dhack45 — Wed, 19 Sep 2007 18:22:35 GMT

We are currently receiving, through our node, xml files which include compressed binary attachments within an element. We would like to decompress , read and load the xml along with the attachment into our backend database. Can someone suggest a process to which we can use to unzip the binary content?

Thanks

Forum: General Discussion Forum

Share your project ideas and find new partners

rakouskask — Thur, 13 Sep 2007 22:19:30 GMT

The Exchange Network is all about collaboration and innovation. To that end, we want to encourage you to use this space to share your new ideas with the rest of the Exchange Network community. So post your thoughts, whether they're fully cooked or just half-baked. There are bound to be others out there with similar interests willing to work with you and share their knowledge. Also, don't forget to visit the Progress section of the Exchange Network website at http://www.exchangenetwork.net/progress. That will give you a snapshot of the exchanges that different partners are working on and it also contains contact information to help you connect with them.

Forum: Network Project Ideas - Share your ideas and find project partners.

Congratulations!

jacorob — Thur, 13 Sep 2007 16:53:11 GMT

Just wanted to say congratulations to the Exchange Network for the progress and getting all 50 states and 7 tribes operational! That's an awesome milestone!

Bob

Forum: General Discussion Forum

Questions when developing a new dataflow

jacorob — Fri, 17 Aug 2007 16:27:24 GMT

I'm working on developing a rather simple schema and trying to follow the rules defined in the various EN documentation. Overall the documentation has been extremely helpful in this endeavor and I appreciate all the obvious hard work that was put in to creating them. I've run in to a few discrepancies while reading the various documentation that caused me some initial confusion and missteps. To help others, and make sure I'm not misinterpreting the documentation, I'd like to outline these issues. I'd also have some questions and an overall suggestion.

Discrepancies
Here are the main documents I'm using to determine the rules in developing the schema
1. XML Schema Design Rules and Conventions (versions 1.1 and 1.0) - referenced as DRC below
2. Namespace Organization, Naming, and Schema File Location (version 1.11) - reference as Namespace document below
3. Shared Schema Components Usage Guide (version 2.0) - reference as SSC Usage Guide below

At this point, my main source of confusion has been figuring out the correct way to organize my file structure, namespace, what xsds should be created (Component, Message, etc), and how the files should be named and referred to.

1. Shared/SimpleContent File Naming
The SSC usage guide appears to conflict with the rule GD2-E in the DRC (v1.1).

The DRC specifies that a 'Shared' schema (defined in DRC Section 1.3) should be named FlowName + '_Shared' + '_v' + Version + '.xsd'.

The SSC Usage guide specifies using a file called 'YourFlowPrefix_SimpleContent_v1.0.xsd' (e.g. - Section 4.2.5)

Conclusion: The SSC Usage guide is slightly out of step with the DRC. The naming convention outlined in the DRC must be used. I would like to say that the SSC Usage guide was extremely helpful for determining how to perform the necessary schema extensions and restrictions!

2. Component Schema File Naming
The SSC usage guide appears to conflict with the rule GD2-D in the DRC (v1.1).

The DRC specifies that a 'Component' schema (defined in DRC Section 1.3) should be named FlowName + 'ComponentName' + '_v' + Version + '.xsd'.

The SSC Usage guide specifies using a file called 'YourFlowPrefix_SSCBlockName_V1.0.xsd' (e.g. - Section 4.2.5). Assuming this is analogous to a Component Schema as defined by the DRC, it does not include the FlowCategoryName.

Conclusion: The SSC Usage guide is slightly out of step with the DRC. The naming convention outlined in the DRC must be used.

3. Elements within Component Schema
When customizing an SSC (e.g. Section 4.2.5), the SSC usage guide specifies that one should create an element for the customized datatype within the same file as the datatype. However, the DRC Section 1.3 states that 'Component schema should only contain complex datatype definitions, not elements or simple types.'

Conclusion: The SSC Usage guide is slightly out of step with the DRC. The rule outlined in the DRC must be used.

4. Root Schema and Message Schema
The Namespace document includes the following line in Section 5.1.1 'Note that a root schema does not itself need to be a message schema'. This implies that a root schema could be a Message schema. However, this may conflict with the DRC Section 1.3 which states that there must be at least one Message schema. In the case of a simple schema which only has one 'message', the DRC appears to require a root schema and a message schema, whereas the Namespace document leaves room for allowing these two schemas to be combined (as the root schema).

Conclusion: Use the DRC and define both a root schema and a message schema - even if the root schema only includes the single message schema.

5. Namespace document uses incorrect naming convention
Section 5.1.1 of the Namespace document specifies the following for naming the root schema:
category _major.minor.xsd

However, per the DRC this should be category _vmajor.minor.xsd (note the 'v' in front of the major.minor).

Conclusion: Simple mistake. The rest of the Namespace document and examples within it use the 'v'

Questions
1. Common components across sub-categories.
The Namespace document (4.1.3) specifies that if components are shared across sub-categories within a flow then a separate sub-category should be created for these shared components. Are there standards for how this sub-category should be named (e.g. - Shared or Common)? Does this sub-category need to follow the same conventions in the DRC (Section 1.3 and Section 3.2)? If so, how do the various schema types map to this shared sub-category? For example, what would a Message schema be?

2. The DRC defines rule in Section 3.1.2 as a 'Should' rule to wrap recurring simple content in a container element. The use of the term 'simple content' in the title confuses me in that it implies in other cases a recurring element should not be wrapped in a container element. If this is the case, in what circumstances should the recurring element not be wrapped?

3. The DRC defines Component Schema and Local Shared Schema. It states that component schema should only contain complex datatypes (not simple types) while Local Shared Schema can contain simple or complex datatypes. Since component schema can include other component schema, are there any guidelines for when a complex datatype should be defined in the Local Shared Schema vs a separate Component Schema?

4. How does one go about 'reserving' a category name?

5. Is it possible to put draft XML schemas in to a development EN registry? It would be helpful during development of the schema to allow the various 'includes' within the schema to function appropriately when sharing the schema for review among IPT members and for testing.

Suggestion
1. While the amount of documentation of the standards and rules is great, it is difficult to put the big picture together from the separate documents. An example 'reference' schema would clarify a lot of questions that may arise. I would suggest that the reference not be an actual production dataflow, but an example that can be easily updated as rules are changed or clarified. It would also not have to demonstrate every single rule outlined in the DRC. A great start would be to outline the various versioning, file naming, and SSC usage rules. It could then be incrementally built upon to include additional rule examples as needed.

Again, I think it is fantastic that so much documentation exists for creating new data flows. Given the amount of documentation, the fact that I only found the few minor discrepancies speaks volumes!

Forum: General Discussion Forum

Implementor of Record (IOR)

tnasset — Wed, 11 Jul 2007 17:23:46 GMT

As I am looking through the RCRA Flow Configuration and Translator Guide I'm seeing that we can only update/delete certain records when we are the Implementor of Record. How would I be able to tell who the IOR is? I don't see this as a field in any of the Handler table definitions and the documentation is rather vague. Is it based on the Activity Location field?

Tracy Nasset
AZ Dept of Environmental Quality

Forum: Draft RCRAInfo Schema

Node vs SEDD

mbreithart — Wed, 20 Jun 2007 18:04:19 GMT

The EPA Superfund Contract Laboratory Program is requesting that Michigan submit laboratory analytical data using a technology called SEDD (see http://www.epa.gov/superfund/programs/clp/sedd.htm). This seems redundant and places an additional burden on the states since the Node, CDX and the eDWR schema already exist and are in use.

Has the eXchange Network attempted to combine these competing data submission formats into one? Preferable the use the Node technology.

//mark breithart

Forum: General Discussion Forum

General Comments and Questions [Post here]

Node2_Team — Sat, 28 Apr 2007 16:52:08 GMT

Respond to this post to make general comments or post questions

Forum: General Discussion Forum

"Free" Node Client Implementation (Java version) - Problems Compiling with JDK1.5 and how to overcome it

mchaganthi — Wed, 13 Dec 2006 16:25:07 GMT

Good Morning

Just started wading around the EPA site for a POC CDX client for starters.

I picked up the free implementation
http://test.epacdxnode.net/CDX_NODE_DNC.zip

and tried to compile the source with JDK 1.5. The compilation fails due to usage of reserved keywords for package the gov.epa.cdx.axis.security.enum. Pasted error message at the bottom of this message.

Then I changed the ant build script to use -source="1.4" and the client compiled with 7 warnings.

I could then successfully run the client and invoke all operations that were implemented by this implementation. Thanks to Joe@helpdesk for bearing with me, answering my questions and giving me the updated wsdl url for locator.properties.

Just thought I'd share my experience so that it might help others coming after me.

If there are other implications of using EPA CDX Node and Client in a JDK 1.5 environment, please let me know. I don't anticipate any since all invocations are happening via WS calls but again, I am a newbie at this.

Regards
Madhu Chaganthi
Northrop Grumman IT
Solutions/Technical Architect
EPHTN - CDC/NCEH - Atlanta

compile:
    Compiling 7 source files to C:\DNC\CDX_DNC\bin\src
    C:\DNC\CDX_DNC\src\gov\epa\state\sample\axis\DNCSampleImpl.java:9: a
s of release 1.5, 'enum' is a keyword, and may not be used as an identifier
    (try -source 1.4 or lower to use 'enum' as an identifier)
    import gov.epa.cdx.axis.security.enum.AuthMethod;
                                      ^
    C:\DNC\CDX_DNC\src\gov\epa\state\sample\security\SecurityMgr.java:5:
as of release 1.5, 'enum' is a keyword, and may not be used as an identifier
    (try -source 1.4 or lower to use 'enum' as an identifier)
    import gov.epa.cdx.axis.security.enum.AuthMethod;
                                      ^
    2 errors

Forum: General Node Forum

xaware node inter agency submit capabilities

dhack45 — Sun, 19 Nov 2006 22:16:15 GMT

Are there any states using the Xaware node product to send and receive inter agency xml files?

Thanks.

Forum: General Discussion Forum