Commits 1276 and 1281 do the same thing to
the trunk and 2.2.x branches, respectively.
Unfortunately, commit 1281 (to the 2.2.x branch)
didn't include the GetPositionMD class, so you get a ClassNotFoundException on startup 
and presumably
that functionality doesn't work in the 2.2.x branch.
--
Richard Walker
Software Improvements Pty Ltd
Phone: +61 2 6273 2055
Fax: +61 2 6273 2082
I wrote:
Commits 1276 and 1281 do the same thing to
the trunk and 2.2.x branches, respectively.
Unfortunately, commit 1281 (to the 2.2.x branch)
didn't include the GetPositionMD class, so you get a ClassNotFoundException on startup
that functionality doesn't work in the 2.2.x branch.
I just realised I was wrong to say "presumably" -
the 2.2.x branch is _really_ broken (and has been
for six weeks now). To see this:
1. Install a fresh checkout of the 2.2.x branch and
start it up.
2. On the front page, in the "Featured map", click
on the "...more..." link to see the metadata.
3. You _should_ see nicely formatted metadata.
Instead, you see the metadata as one continuous
bit of text.
I have confirmed that commit 1280 works, that
commit 1281 doesn't, and that adding GetPositionMD.java
to commit 1281 and recompiling fixes the problem.
So . . . please commit the missing GetPositionMD.java file
to the 2.2.x branch.
--
Richard Walker
Software Improvements Pty Ltd
Phone: +61 2 6273 2055
Fax: +61 2 6273 2082
FYI, I committed the file. That was an oversight on my part.
Ciao,
Jeroen
On May 29, 2008, at 5:03 AM, Software Improvements gn-devel wrote:
I wrote:
Commits 1276 and 1281 do the same thing to
the trunk and 2.2.x branches, respectively.
Unfortunately, commit 1281 (to the 2.2.x branch)
didn't include the GetPositionMD class, so you get a
ClassNotFoundException on startupand presumably
that functionality doesn't work in the 2.2.x branch.I just realised I was wrong to say "presumably" -
the 2.2.x branch is _really_ broken (and has been
for six weeks now). To see this:1. Install a fresh checkout of the 2.2.x branch and
start it up.
2. On the front page, in the "Featured map", click
on the "...more..." link to see the metadata.
3. You _should_ see nicely formatted metadata.
Instead, you see the metadata as one continuous
bit of text.I have confirmed that commit 1280 works, that
commit 1281 doesn't, and that adding GetPositionMD.java
to commit 1281 and recompiling fixes the problem.So . . . please commit the missing GetPositionMD.java file
to the 2.2.x branch.--
Richard Walker
Software Improvements Pty Ltd
Phone: +61 2 6273 2055
Fax: +61 2 6273 2082-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
ISSUE:
How to deal with specific instances of one class that refer to only one
instance of another class.
Context
ISO 19115 / ISO 19139 allows for multiple instances of a range of
classes.
ISO 19115 (non-exclusive list)
MD_Metadata has spatialRepresentationInfo [0..*], referenceSystemInfo
[0..1], identificationInfo [1..*], etc
MD_Distribution has distributionFormat [C..*], transferOptions [0..*],
etc
[ISO19139 allows for @id in the associated class for each of these]
USE CASE:
A record may contain more than one MD_Identification -
MD_DataIdentification (DI), or SV_ServiceIdentification (SI)
When describing a closely coupled service this is logical
(conditionality of srv:operateOn)
(other cases are less obvious)
In one metadata record there could (often should be):
more than one MD_DigitalTransferOption(TO)
more than one MD_Format (DF)
more than one spatial Representation - MD_GridSpatialRepresenation
(GR), MD_VectorSpatialRepresenation (VR), etc
more than one MD_ReferenceSystem (RS)
PROBLEM:
How to relate a specific TO with the appropriate DI/SI, DF, RS, GR,
and VR
SOLUTIONS:
1) UGLY - build a @id in TO that when parsed yields the appropriate
DI/SI, DF, RS, GR, and VR
2) KLUDGY - build a schema to replace MD_DigitalTransferOptions
contains associations - allowing for referential
attribution (xlink:href)
for each of DI/SI, DF, RS, GR, and VR
(refer to
http://adl.brs.gov.au/metadata/gmd/BRS_transferOptions.xsd)
3) ACCEPTABLE - build a schema to replace MD_Metadata that contains a
[0..*] association to a new class
build new class that relates two and only two instances
of aggregate classes (use xs:IDREF)
(refer to
http://adl.brs.gov.au/metadata/gmd/BRS_metadataEntity.xsd)
OUTCOMES:
1) this is feasible, does not break ISO 19115 or ISO 19139 even if it
is not acceptable
Already in use see metadata accessible via http:/adl.brs.gov.au
2) This assumes that the only place that relationships are important is
in the MD_DigitalTransferOptions
If metadata is delivered in this form then need to report a set of
MD_MetadataExtensionInformation
but readily translatable into option 1 (thus no need to report a set
of MD_MetadataExtensionInformation)
3) Allows for previously undefined relationships to be described
Bit harder to manage
QUESTION:
What next?
Cheers
e
Evert Bleys
BRS Data Manager
Biosecurity and Information Sciences
Bureau of Rural Sciences
Department of Agriculture Fisheries and Forestry
GPO Box 855 CANBERRA CITY ACT 2601
Ph +61 (0)2 6272 5627
------IMPORTANT - This message has been issued by The Department of Agriculture, Fisheries and Forestry (DAFF). The information transmitted is for the use of the intended recipient only and may contain confidential and/or legally privileged material. It is your responsibility to check any attachments for viruses and defects before opening or sending them on.
Any reproduction, publication, communication, re-transmission, disclosure, dissemination or other use of the information contained in this e-mail by persons or entities other than the intended recipient is prohibited. The taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this e-mail in error please notify the sender and delete all copies of this transmission together with any attachments. If you have received this e-mail as part of a valid mailing list and no longer want to receive a message such as this one advise the sender by return e-mail accordingly. Only e-mail correspondence which includes this footer, has been authorised by DAFF
------