[Fiware-support] Inundación de mensajes de la lista fusionforge-bugs

Juanjo Hierro jhierro at tid.es
Sun Oct 28 13:14:31 CET 2012


Hola,

  ¿ Hay alguna razón que conozcáis por la que esté empezando a recibir multitud de mensajes de la lista fusionforge-bugs ?

  ¿ Tal vez porque habéis subscrito la lista fiware-support a esa lista o algo así ?

  Saludos,

-- Juanjo Hierro


-------------
Product Development and Innovation (PDI) - Telefonica Digital
website: www.tid.es<http://www.tid.es>
email: jhierro at tid.es<mailto:jhierro at tid.es>
twitter: twitter.com/JuanjoHierro

FI-WARE (European Future Internet Core Platform) Chief Architect

You can follow FI-WARE at:
  website:  http://www.fi-ware.eu
  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
  twitter:  http://twitter.com/FIware
  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932



-------- Original Message --------
Subject:        [fusionforge-Bugs][237] [plugin/oslc] should render complete <rdf:RDF prefix for XML documents
Date:   Sun, 28 Oct 2012 10:54:26 +0100
From:   <fusionforge-bugs at fusionforge.org><mailto:fusionforge-bugs at fusionforge.org>
Reply-To:       <fusionforge-bugs at fusionforge.org><mailto:fusionforge-bugs at fusionforge.org>
To:     <noreply at fusionforge.org><mailto:noreply at fusionforge.org>



fusionforge-Bugs item #237 was changed at 2012-10-28 10:54 by Franck VILLAUME
You can respond by visiting:
https://fusionforge.org/tracker/?func=detail&atid=105&aid=237&group_id=6

Status: Closed
Priority: 3
Submitted By: Olivier Berger (olberger)
Assigned to: Sabri LABBENE (labbenes)
Summary: [plugin/oslc] should render complete <rdf:RDF prefix for XML documents
>Target Release: 5.2
Found in Version: trunk
Severity: major
Resolution: Fixed


Initial Comment:
Hi.

The specs indicate that the XML representation should validate RDF.

Thus the content should contain prefixes for RDF. For instance :

<?xml version="1.0"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"<http://www.w3.org/1999/02/22-rdf-syntax-ns#>
  xmlns:dc="http://purl.org/dc/elements/1.1/"<http://purl.org/dc/elements/1.1/> xmlns:oslc_disc="http://open-services.net/xmlns/discovery/1.0/"<http://open-services.net/xmlns/discovery/1.0/> >
<oslc_disc:ServiceProviderCatalog rdf:about="">
...
</oslc_disc:ServiceProviderCatalog>
</rdf:RDF>

instead of :
<?xml version="1.0"?>
<oslc_disc:ServiceProviderCatalog xmlns:oslc_disc="http://open-services.net/xmlns/discovery/1.0/"<http://open-services.net/xmlns/discovery/1.0/> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"<http://www.w3.org/1999/02/22-rdf-syntax-ns#> rdf:about="">

Thanks in advance.

----------------------------------------------------------------------

Comment By: Olivier Berger (olberger)
Date: 2011-01-19 13:49

Message:
Actually, this may not be problematic as long as there's only one resource, and the <rdf:RDF enclosing entity is not necessary, per RDF/XML specs.

However, its is required (http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixRepresentations#Steps_to_generate_an_XML_represe) that this is done for application/xml representation, so I guess we should do it too for application/rdf+xml

----------------------------------------------------------------------

You can respond by visiting:
https://fusionforge.org/tracker/?func=detail&atid=105&aid=237&group_id=6
.






________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-support/attachments/20121028/fcbb0c84/attachment.html>


More information about the Fiware-support mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy