Custom Query (298 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (19 - 21 of 298)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Ticket Resolution Summary Owner Reporter
#19 wontfix RDF Tagging is inconsistent between different pages Earle Martin IVORW@…
Description

Sat Oct 15 12:53:16 2005 IVORW - Ticket created [Reply] [Comment]

Subject: RDF Tagging is inconsistent between different pages

The RDF tagging scheme for a node with geographical metadata has information under tag <geo:SpatialThing>, including the list of categories.

When there is no geodata, there is no <geo:SpatialThing> tag, but much data you would expect to find here migrates to another <rdf:Description> tag.

We need something consistent if we want to parse this usefully.

Download (untitled) 356b

Download examples.rdf 3.2k

Sun Oct 16 15:03:55 2005 EMARTIN - Correspondence added [Reply] [Comment]

[IVORW - Sat Oct 15 12:53:16 2005]:

When there is no geodata, there is no <geo:SpatialThing> tag, but much data you would expect to find here migrates to another <rdf:Description> tag.

Sorry, I don't understand - what do you mean by "migrates to another <rdf:Description> tag"?

Download (untitled) 286b

Sun Oct 16 17:42:50 2005 IVORW - Correspondence added [Reply] [Comment]

From: IVORW@…

[EMARTIN - Sun Oct 16 15:03:55 2005]:

Sorry, I don't understand - what do you mean by "migrates to another <rdf:Description> tag"?

There is an attachment to the original post, containing two node RDFs, one of which has a geo:SpatialThing, and the other has a second rdf:Description. This is kept for the record, just in case we fix the London website.

http://london.openguides.org/index.cgi?id=AMT_Espresso;format=rdf

This has no geodata, and has dc:subject chefmoz:hours and foaf:homepage tags in a second rdf:Description tag, whereas other nodes have the same info inside their geo:SpatialThing tag (along with address, lat/long etc.)

I have accommodated this in OpenGuides::RDF::Reader, but it's still a bug. Non-geo data should be in one tag or the other.

Download (untitled) 771b

Thu Nov 3 13:55:24 2005 EMARTIN - Correspondence added [Reply] [Comment]

[IVORW - Sun Oct 16 17:42:50 2005]:

There is an attachment to the original post, containing two node RDFs

Oop, missed that, sorry.

This has no geodata, and has dc:subject chefmoz:hours and foaf:homepage tags in a second rdf:Description tag whereas other nodes have the same info inside their geo:SpatialThing tag (along with address, lat/long etc.)

Having opening hours needs to be added to the logic for marking things as spatial - thanks, I'll get on it. Having a homepage doesn't qualify, though, because plenty of virtual-only things have websites.

It would be nice to deduce this information from what categories the item has had assigned (e.g. Coffee Shops) as well, which is something I'll consider.

I have accommodated this in OpenGuides::RDF::Reader, but it's still a bug. Non-geo data should be in one tag or the other.

By the way, are you sure you read the RDF right? Every node has either two rdf:Descriptions or one rdf:Description and one geo:SpatialThing. The first rdf:Description describes the node itself; the second (or geo:SpatialThing) describes the /subject/ of the node. This is a careful distinction that has been the subject of much earlier discussion (in general terms, not our particular implementation - see http://www.w3.org/2001/tag/issues.html#httpRange-14 ).

Download (untitled) 1.2k

Fri Nov 4 14:57:10 2005 DOM - Correspondence added [Reply] [Comment]

[EMARTIN - Thu Nov 3 13:55:24 2005]:

Having opening hours needs to be added to the logic for marking things as spatial - thanks, I'll get on it. Having a homepage doesn't

qualify,

though, because plenty of virtual-only things have websites.

Can't virtual-only things have opening hours too? For example telephone sales agencies and no doubt more.

Download (untitled) 361b

Fri Nov 4 16:31:54 2005 EMARTIN - Correspondence added [Reply] [Comment]

[DOM - Fri Nov 4 14:57:10 2005]:

Can't virtual-only things have opening hours too? For example telephone sales agencies and no doubt more.

I wouldn't call any company that has an office somewhere and a telephone number "virtual". Anyway, they might have operating hours, but not opening hours as I understand it. Actually, http://chefmoz.org/rdf/elements/1.0/ describes opening hours as "A string describing the hours the restaurant is open." This is decidedly suboptimal, considering that not everything is a restaurant, and I would like to rapidly find an alternative.

Download (untitled) 577b

Fri Nov 4 16:33:39 2005 EMARTIN - Correspondence added [Reply] [Comment]

[EMARTIN - Fri Nov 4 16:31:54 2005]:

I would like to rapidly find an alternative.

On this point, see also http://esw.w3.org/topic/OpeningHoursUseCase .

#20 fixed custom_node.tt support (diff included) Dominic Hargreaves daniel@…
Description

Sun Oct 16 11:54:31 2005 guest - Ticket created [Reply] [Comment]

Subject: custom_node.tt support (diff included)

Request for custom_node.tt so i can put things after the content.

My preferred change would be:

node.tt 30a31,32

[% INCLUDE custom_node.tt %]

Thanks,

Daniel Admin of Open Guide to Southampton

#21 fixed Website metadata allows invalid characters which break the RDF feed Dominic Hargreaves IVORW@…
Description

Mon Oct 17 03:00:04 2005 IVORW - Ticket created [Reply] [Comment]

Subject: Website metadata allows invalid characters which break the RDF feed

Currently, no syntax validation is performed on the field "website". This actually allows square bracket syntax, such as the page:

http://london.openguides.org/index.cgi?Peckham_Rye_Common_And_Park

Unfortunately, this cleverness breaks anything parsing the RDF data (attached).

Either this metadata field should be validated more strictly in the commit function (probably a good idea), or we should at least cater for square bracket links in the RDF feed.

Download (untitled) 458b

Download Peckham_Rye_Common_And_Park.rdf 1.7k

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Note: See TracQuery for help on using queries.