elective-stereophonic
elective-stereophonic
Aliases as DNS
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.2

Pages: 1 [2]  All

Author Topic: Aliases as DNS  (Read 7494 times)

wastedbit

  • Newbie
  • *
  • Karma: +0/-0
  • Offline Offline
  • Posts: 5
    • View Profile
Re: Aliases as DNS
« Reply #20 on: July 05, 2014, 03:06:59 pm »

Might the community support a XML string in the data field.  Then, you could layer on tags as you wish.  How large can the DATA field in an alias be?

Alias Data:

<?xml version="1.0" encoding="utf-8"?>
<name>Barack Obama</name>
<url>mysite.com</url>
<image>link to picture</image>
<mailingAddress>
   <mailingName>Barack Obama</mailingName>
   <mailingAddress>1600 Pennsylvania Ave NW</mailingAddress>
   <mailingCity>Washington</mailingCity>
   <mailingState>MD</mailingState>
   <mailingZipCode>20500</mailingZipCode>
   <mailingCountry>USA</mailingCountry>
</mailingAddress>

The idea is for an online identity.  This one would feature an express checkout as alias has the mailing address. 
Logged

benjyz

  • Hero Member
  • *****
  • Karma: +71/-4
  • Offline Offline
  • Posts: 508
    • View Profile
Re: Aliases as DNS
« Reply #21 on: July 05, 2014, 08:00:15 pm »

Im just using the URI field, in the gui if you change the alias type to "other" then the URI field is renamed to data.

Thanks. There are 1-2 bugs in the UI with regards to aliases. Each data update costs 1 nxt, also. Not ideal at the moment - I will experiment a bit with this.
Logged

slothbag

  • Sr. Member
  • ****
  • Karma: +74/-4
  • Offline Offline
  • Posts: 454
    • View Profile
Re: Aliases as DNS
« Reply #22 on: July 05, 2014, 11:01:30 pm »

Might the community support a XML string in the data field.  Then, you could layer on tags as you wish.  How large can the DATA field in an alias be?

Alias Data:

<?xml version="1.0" encoding="utf-8"?>
<name>Barack Obama</name>
<url>mysite.com</url>
<image>link to picture</image>
<mailingAddress>
   <mailingName>Barack Obama</mailingName>
   <mailingAddress>1600 Pennsylvania Ave NW</mailingAddress>
   <mailingCity>Washington</mailingCity>
   <mailingState>MD</mailingState>
   <mailingZipCode>20500</mailingZipCode>
   <mailingCountry>USA</mailingCountry>
</mailingAddress>

The idea is for an online identity.  This one would feature an express checkout as alias has the mailing address.

I think json is probably a better choice, less verbose and more widely used in the Crypto space.
Logged

benjyz

  • Hero Member
  • *****
  • Karma: +71/-4
  • Offline Offline
  • Posts: 508
    • View Profile
Re: Aliases as DNS
« Reply #23 on: July 06, 2014, 11:09:56 am »

Might the community support a XML string in the data field.  Then, you could layer on tags as you wish.  How large can the DATA field in an alias be?

Alias Data:

<?xml version="1.0" encoding="utf-8"?>
<name>Barack Obama</name>
<url>mysite.com</url>
<image>link to picture</image>
<mailingAddress>
   <mailingName>Barack Obama</mailingName>
   <mailingAddress>1600 Pennsylvania Ave NW</mailingAddress>
   <mailingCity>Washington</mailingCity>
   <mailingState>MD</mailingState>
   <mailingZipCode>20500</mailingZipCode>
   <mailingCountry>USA</mailingCountry>
</mailingAddress>

The idea is for an online identity.  This one would feature an express checkout as alias has the mailing address.

I think json is probably a better choice, less verbose and more widely used in the Crypto space.

JSON is unstructured. For these kinds of applications structured data makes more sense, i.e. limited trees, not arbitrary expressions. One common problem is: somebody defines a structured data format, and then another person wants to add a field. For example HTML has a number of known tags, and browser interpret those tags. Those are the reasons there are RFC's and language committees.
Logged

sile16

  • Jr. Member
  • **
  • Karma: +6/-0
  • Offline Offline
  • Posts: 38
    • View Profile
    • Everyday Crypto
Re: Aliases as DNS
« Reply #24 on: July 06, 2014, 03:44:31 pm »

Definitely json, XML takes up too many characters, hard to read.  JSON is the preferred method.  I believe the field is limited to 1000 bytes.



Logged

benjyz

  • Hero Member
  • *****
  • Karma: +71/-4
  • Offline Offline
  • Posts: 508
    • View Profile
Re: Aliases as DNS
« Reply #25 on: July 06, 2014, 05:33:19 pm »

JSON is an unstructured data format. A bad choice for something like DNS. There was a lot of effort to build something like OWL on top of XML, but it never worked, see http://en.wikipedia.org/wiki/Web_Ontology_Language
Logged

sile16

  • Jr. Member
  • **
  • Karma: +6/-0
  • Offline Offline
  • Posts: 38
    • View Profile
    • Everyday Crypto
Re: Aliases as DNS
« Reply #26 on: July 07, 2014, 03:16:50 am »

We kind of got sidetracked on JSON vs XML, ultimately it doesn't matter as long as the system is functional and we can get user adoption.  However, one other big benefit to trying to stay pretty close to what namecoin is doing is that we could potentially have a single client that can resolve both .bit domains as well as .nxt domains.

Namecoin DSN spec: _https://wiki.namecoin.info/index.php?title=Domain_Name_Specification
Namecoin ID spec: _https://wiki.namecoin.info/index.php?title=Identity


Also, this topic is kind of being duplicated over at :

https://nxtforum.org/general-discussion/nxt-dnsaliases-resolver/

which I just did a huge post in... 
Logged

qq2536007339

  • Hero Member
  • *****
  • Karma: +42/-9
  • Offline Offline
  • Posts: 514
    • View Profile
Re: Aliases as DNS
« Reply #27 on: October 06, 2015, 08:39:28 am »

I also don't know why aliases were designed this way. Why was not the full UTF-8 range allowed?

Since you are the core dev now,would you like to expand aliases to full UTF-8?
Logged
你送我阿朵,我是要的。ARDOR-DJ68-PG7W-4JEU-2LU5T
Pages: 1 [2]  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly