[Esip-discovery] Fwd: OpenSearch Description and ATOM Documents Validation
Steve Richard
steve.richard at azgs.az.gov
Thu Jul 11 20:00:29 EDT 2013
W3CDTF ( <http://www.w3.org/TR/NOTE-datetime>
http://www.w3.org/TR/NOTE-datetime) is only a ‘recommendation’ according to
the dc documentation (
<http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=elements#elements-
date>
http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=elements#elements-d
ate); the XML schema at
http://www.dublincore.org/schemas/xmls/qdc/2008/02/11/dc.xsd implements date
as any simple content. (Golly, I love Dublin Core, its soooooo flexible)
Anyway the W3CDTF doesn’t look like it allows intervals, that’s probably why
the validator gagged (although what’s in the atom is technically correct*,
since there’s no binding to a profile anywhere
).
steve
Stephen M Richard
Arizona Geological Survey
416 W. congress #100
Tucson, AZ
AZGS: 520-770-3500
Office: 520-209-4127
FAX: 520-770-3505
<?xml version="1.0" encoding="UTF-8"?>
<simpledc xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://www.dublincore.org/schemas/xmls/qdc/20
08/02/11/simpledc.xsd">
<dc:date>2002-04-29T04:35:38Z/2002-04-29T05:19:53Z</dc:date>
</simpledc>
is valid according to Oxygen
From: esip-discovery-bounces at lists.esipfed.org
[mailto:esip-discovery-bounces at lists.esipfed.org] On Behalf Of Doug Newman
Sent: Monday, July 08, 2013 5:09 AM
To: Pedro Gonçalves
Cc: esip-discovery at lists.esipfed.org
Subject: Re: [Esip-discovery] Fwd: OpenSearch Description and ATOM Documents
Validation
Pedro,
we have been using this as a valdation mechanism and have incorporated some
fixes in 10.64
http://validator.w3.org/feed/
to test our responses and it gives us the same error (and others)
1. <id>G1000088617-OBPG</id> id must be a full and valid URL:
G1000088617-OBPG - this will be fixed in our 10.64 release
2. dc:date must be an W3CDTF date: 2002-04-29T04:35:38Z/2002-04-29T05:19:53Z
- odd, this looks valid to me
3. Missing content or alternate link - which is the issue you found. - this
will be fixed in our 10.64 release
10.64 is already in partner test and is hooked up to the operational
inventory,
Try this url,
https://api-test.echo.nasa.gov/opensearch/granules.atom?clientId=
<https://api-test.echo.nasa.gov/opensearch/granules.atom?clientId=&shortName
=MERIS_L1B_RR&versionId=1&dataCenter=OBPG>
&shortName=MERIS_L1B_RR&versionId=1&dataCenter=OBPG
Cheers,
Doug Newman - ECHO Operations Lead
douglas.j.newman at nasa.gov
douglas.newman at vangent.com
Vangent, A General Dynamics Company | NASA | ECS Evolution Development
Program
http://earthdata.nasa.gov/echo
Note: I am not a government employee and have no legal authority to obligate
any federal, state, or local government to perform any action of payment.
On 7/7/13 7:59 AM, Pedro Gonçalves wrote:
Hi Doug
Unfortunately it fails on the ATOM schematron rules with
Element: feed/entry[1]
rule = atom:link[@rel='alternate'] or atom:link[not(@rel)] or atom:content
An atom:entry must have at least one atom:link element with a rel attribute
of 'alternate' or an atom:content.
for all entries ...
We can discuss this better, but my general idea is to develop compliance
levels, first atom (rfc4287), then geo/time (ogc 10-032), and then to
develop a special schema to take in consideration the rules from the esip
best practice.
cheers
Pedro
On Jul 5, 2013, at 10:00 PM, Doug Newman <mailto:douglas.j.newman at nasa.gov>
<douglas.j.newman at nasa.gov> wrote:
Pedro,
the suspense is killing me, did
curl 'https://api.echo.nasa.gov/opensearch/granules.atom?clientId=
<https://api.echo.nasa.gov/opensearch/granules.atom?clientId=&shortName=MERI
S_L1B_RR&versionId=1&dataCenter=OBPG>
&shortName=MERIS_L1B_RR&versionId=1&dataCenter=OBPG' | sh rncv.sh -s
../schemas/atom/2005/rfc4287.rnc
validate?
Doug Newman - ECHO Operations Lead
douglas.j.newman at nasa.gov
douglas.newman at vangent.com
Vangent, A General Dynamics Company | NASA | ECS Evolution Development
Program
http://earthdata.nasa.gov/echo
Note: I am not a government employee and have no legal authority to obligate
any federal, state, or local government to perform any action of payment.
On 7/5/13 3:56 PM, Lynnes, Christopher S. (GSFC-6102) wrote:
FYI:
Begin forwarded message:
From: Pedro Gonçalves <mailto:pereira.goncalves at gmail.com>
<pereira.goncalves at gmail.com>
Subject: OpenSearch Description and ATOM Documents Validation
Date: July 1, 2013 1:55:33 PM EDT
To: <mailto:opensearch at googlegroups.com> "opensearch at googlegroups.com"
<mailto:opensearch at googlegroups.com> <opensearch at googlegroups.com>
Reply-To: <mailto:opensearch at googlegroups.com>
"opensearch at googlegroups.com" <mailto:opensearch at googlegroups.com>
<opensearch at googlegroups.com>
Hi
For the validation of some atom feeds from an ongoing project I created a
few RelaxNG Compact Syntax Schemas with ISO Schematron rules of Atom,
OpenSearch and extensions files that might be of interest to the group.
https://github.com/Terradue/trax/tree/master/relaxng/schemas
I covered the OpenSearch core, and Geo, Time and Parameter extensions.
I plan to add the other extensions in the future.
For now I made a script that joins the several java jar and xsl files and
performs an one-step validation procedure.
https://github.com/Terradue/trax/tree/master/relaxng/scripts
You can validate local file with
sh rncv.sh -s ../schemas/opensearch/1.1/osatom.rnc -f
../examples/atom/atomeo01_noauthor.xml
or you can validate an external server
curl 'https://api.echo.nasa.gov/opensearch/granules.atom?clientId=
<https://api.echo.nasa.gov/opensearch/granules.atom?clientId=&shortName=MERI
S_L1B_RR&versionId=1&dataCenter=OBPG>
&shortName=MERIS_L1B_RR&versionId=1&dataCenter=OBPG' | sh rncv.sh -s
../schemas/atom/2005/rfc4287.rnc
I tested this extensively the last weeks but let me know if you find any
issue/problems
cheers
Pedro
--
You received this message because you are subscribed to the Google Groups
"OpenSearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opensearch+unsubscribe at googlegroups.com.
To post to this group, send email to opensearch at googlegroups.com.
Visit this group at http://groups.google.com/group/opensearch.
For more options, visit https://groups.google.com/groups/opt_out.
--
Dr. Christopher Lynnes NASA/GSFC, Code 610.2 phone: 301-614-5185
_______________________________________________
Esip-discovery mailing list
Esip-discovery at lists.esipfed.org
http://www.lists.esipfed.org/mailman/listinfo/esip-discovery
_______________________________________________
Esip-discovery mailing list
Esip-discovery at lists.esipfed.org
http://www.lists.esipfed.org/mailman/listinfo/esip-discovery
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.esipfed.org/pipermail/esip-discovery/attachments/20130711/509912c1/attachment.html>
More information about the Esip-discovery
mailing list