As you certainly know the European commission has publish a draft proposal
named INSPIRE concerning the implementing rules on metadata for the member
of Europe. The version3 is publish and open to public consultation until the
21 December.
I try to implement the rules on metadata using Geonetwork, and i have a
problem with two fields.
for the validation step.
1 ) The first is the resolution distance :
//IdentificationInfo/spatialResolution/distance
Geonetwork create the xml like that :
<gco:Distance>3</gco:Distance>
And the validation don't work so i add manually the “uom” element on the xml
for the validation
<gco:Distance uom="Metres">3</gco:Distance>
Is it possible to add automatically this field ?
uom is not a mandatory attribute on gco:Distance but doesn't seem to be appearing even when you force gco:Distance to show both content and attributes using a special template - I've got some changes planned for the editor code on attributes but this appears to be a bug even in my changes so thanks for pointing this out. I'll fix it and commit it but see below for when...
2 ) The second point concern the TemporalExtent element
//IdentificationInfo/extent/temporalElement
Is that corrected on the trunk ?
If that ok, which files are concerned ? I wish i can get changed files to
compile my own version working with the stable sources branches 2.1
Not in the trunk yet as far as I know - its related to fixing the <choice> blocks used in the gml schema so that they work correctly in the editor - I do have a properly working copy in my 2.0.3 test code but I haven't committed it to the 2.1 trunk yet. Hopefully in a few days...
With the additional code to handle these schema complications, I have a strong feeling that a shift to XFORMs for XML editing is becoming more and more attractive.
As you certainly know the European commission has publish a draft proposal
named INSPIRE concerning the implementing rules on metadata for the member
of Europe. The version3 is publish and open to public consultation until the
21 December.
I try to implement the rules on metadata using Geonetwork, and i have a
problem with two fields.
for the validation step.
1 ) The first is the resolution distance :
//IdentificationInfo/spatialResolution/distance
Geonetwork create the xml like that :
<gco:Distance>3</gco:Distance>
And the validation don't work so i add manually the “uom” element on the xml
for the validation
<gco:Distance uom="Metres">3</gco:Distance>
Is it possible to add automatically this field ?
The following should say that uom IS a mandatory attribute on gco:distance! Apologies, I somehow typed "not" in there!
uom is not a mandatory attribute on gco:Distance but doesn't seem to be appearing even when you force gco:Distance to show both content and attributes using a special template - I've got some changes planned for the editor code on attributes but this appears to be a bug even in my changes so thanks for pointing this out. I'll fix it and commit it but see below for when...
2 ) The second point concern the TemporalExtent element
//IdentificationInfo/extent/temporalElement
Is that corrected on the trunk ?
If that ok, which files are concerned ? I wish i can get changed files to
compile my own version working with the stable sources branches 2.1
Not in the trunk yet as far as I know - its related to fixing the <choice> blocks used in the gml schema so that they work correctly in the editor - I do have a properly working copy in my 2.0.3 test code but I haven't committed it to the 2.1 trunk yet. Hopefully in a few days...
With the additional code to handle these schema complications, I have a strong feeling that a shift to XFORMs for XML editing is becoming more and more attractive.
Sure for the moment template are very usefull but they are simple copy.
inheritance for element like point of contact and other will be very
suitable.
Anyway do you know if it is planned to implement a functionality like that
in the future ?
I do not know if it is linked but sometime when we delete or add new element
on metadata the scrollbar loose the original position on metadata editing it
is a little boring for users, do you think XFORMs can fix that problem.
I drift from my original question ...
Thank you for your answer Simon.
Simon Pigot-5 wrote:
FBachraty wrote:
Hello,
As you certainly know the European commission has publish a draft
proposal
named INSPIRE concerning the implementing rules on metadata for the
member
of Europe. The version3 is publish and open to public consultation until
the
21 December.
I try to implement the rules on metadata using Geonetwork, and i have a
problem with two fields.
for the validation step.
1 ) The first is the resolution distance :
//IdentificationInfo/spatialResolution/distance
Geonetwork create the xml like that :
<gco:Distance>3</gco:Distance>
And the validation don't work so i add manually the “uom” element on the
xml
for the validation
<gco:Distance uom="Metres">3</gco:Distance>
Is it possible to add automatically this field ?
uom is not a mandatory attribute on gco:Distance but doesn't seem to be
appearing even when you force gco:Distance to show both content and
attributes using a special template - I've got some changes planned for
the editor code on attributes but this appears to be a bug even in my
changes so thanks for pointing this out. I'll fix it and commit it
but see below for when...
2 ) The second point concern the TemporalExtent element
//IdentificationInfo/extent/temporalElement
Is that corrected on the trunk ?
If that ok, which files are concerned ? I wish i can get changed files to
compile my own version working with the stable sources branches 2.1
Not in the trunk yet as far as I know - its related to fixing the
<choice> blocks used in the gml schema so that they work correctly in
the editor - I do have a properly working copy in my 2.0.3 test code but
I haven't committed it to the 2.1 trunk yet. Hopefully in a few days...
With the additional code to handle these schema complications, I have a
strong feeling that a shift to XFORMs for XML editing is becoming more
and more attractive.
I have a strong feeling that a shift to XFORMs for XML editing is
becoming more
and more attractive.
Does XFORM can facilitate creation of inheritance beetween metadata ?
Not really, xForm could help on the client side to have a more
interactive editor:
- using xForms, the client side deals with an XML tree which is created
by the browser as the user add elements and not with key value pair
(KVP) as we have actually.
- xforms engine is usually based on ajax
- xforms could support validation against schema types
- xforms allows defining rules between elements (eg. element a is
mandatory if b is greater than 10, ...) : close to what schematron does
i think
But I've never tried to deals with ISO xml tree on the client side ...
maybe too big ?
For inheritance, it has to be done on the server side using xlink ...
there was some job on sub-template, but I don't really know how far we
are on the implementation ? Jeroen comments on that ?
Sure for the moment template are very usefull but they are simple copy.
inheritance for element like point of contact and other will be very
suitable.
Anyway do you know if it is planned to implement a functionality like that
in the future ?
I do not know if it is linked but sometime when we delete or add new element
on metadata the scrollbar loose the original position on metadata editing it
is a little boring for users, do you think XFORMs can fix that problem.
I drift from my original question ...
Thank you for your answer Simon.
Simon Pigot-5 wrote:
FBachraty wrote:
Hello,
As you certainly know the European commission has publish a draft
proposal
named INSPIRE concerning the implementing rules on metadata for the
member
of Europe. The version3 is publish and open to public consultation until
the
21 December.
I try to implement the rules on metadata using Geonetwork, and i have a
problem with two fields.
for the validation step.
1 ) The first is the resolution distance :
//IdentificationInfo/spatialResolution/distance
Geonetwork create the xml like that :
<gco:Distance>3</gco:Distance>
And the validation don't work so i add manually the “uom” element on the
xml
for the validation
<gco:Distance uom="Metres">3</gco:Distance>
Is it possible to add automatically this field ?
uom is not a mandatory attribute on gco:Distance but doesn't seem to be
appearing even when you force gco:Distance to show both content and
attributes using a special template - I've got some changes planned for
the editor code on attributes but this appears to be a bug even in my
changes so thanks for pointing this out. I'll fix it and commit it
but see below for when...
2 ) The second point concern the TemporalExtent element
//IdentificationInfo/extent/temporalElement
Is that corrected on the trunk ?
If that ok, which files are concerned ? I wish i can get changed files to
compile my own version working with the stable sources branches 2.1
Not in the trunk yet as far as I know - its related to fixing the
<choice> blocks used in the gml schema so that they work correctly in
the editor - I do have a properly working copy in my 2.0.3 test code but
I haven't committed it to the 2.1 trunk yet. Hopefully in a few days...
With the additional code to handle these schema complications, I have a
strong feeling that a shift to XFORMs for XML editing is becoming more
and more attractive.
--
Francois Xavier Prunayre
Camptocamp France SAS
Savoie Technolac, BP 352
73377 Le Bourget du Lac Cedex
Tel : + 33 (0)6 34 11 71 75 http://www.camptocamp.com
francois-xavier.prunayre@anonymised.com
so thanks for pointing this out. I'll fix it and commit it but see below for when...
